Currently, when a patch on the MetaModule approaches its processing limit it just stops playing.
However, there is no visual feedback to identify per-module CPU consumption, making it difficult to optimize patches or identify “heavy” modules.
I suggest adding a list of active modules in the current patch, sorted by their CPU impact.
Does that make sense?