How about no? How about the obvious? Not all newbie scripters have the cognitive capability to find a new village. Think: can you REPRODUCE the problem by inserting a break into the popups section? I sure couldn't. How is the popups section even relevant when ALL remotes, aliases and popups are affected?
You can reproduce this "faulty script in popups using break" (which by the way, won't ever produce that message) by the following steps:
1. Type /timerTESTLOOP 0 0 var %x = 0 | while (%x < 100) { inc %x }
This is merely just to emulate the affect of a short loop that is called constantly.
2. Press, and hold, CTRL. Wait a second, then press, and hold, PAUSE/BREAK. Wait a second, then press, and hold SCROLL LOCK. If you aren't getting "Break" errors 3 or 4 times a second by now, release the keys, and switch windows, then try again.
3. Type any non-internal/remote/alias command, for example /j. Open any popup that is scripted. Etc, etc.
How to stop it? Hold CTRL, and tap PAUSE/BREAK repeatedly.
Yes, turns out it is something similar to "keys being stuck". More like a software emulation of a stuck key. I don't think this is a bug. It can come in handy, having a repetitious break function. It's just not known about (as you can see, there are no solutions on the mIRC forum for this activity). I've run into it myself, and usually after pressing CTRL+PAUSE/BREAK, so after thinking of everything possible to try to break scripts in this manner, particularly loops (as I remembered), I stumbled across this by accident.
I hope you guys enjoy this rather ignorantly hidden feature as much as I recently have
Enjoy!
edit: to turn the timer off, /timerTESTLOOP off