1. $ticks - %t is not a milliseconds value.
2. That wouldn't really help pinpoints slowdowns in a large blackbox as Deathwolf is describing.
@Deathwolf: Unfortunately, there's no way to tell what part of a script is slowing you down besides manually testing each event independently of others. I'd unload scripts until the slowdown is gone then focus on the last file you unloaded... assuming you have scripts loaded.
Also look at loaded dlls by typing //echo -a $dll(0) to see if you have any loaded and then $dll(1) $dll(2) ... to the number returned by $dll(0) to see each file. You can unload them with //dll -u $dll(N)
No dlls loaded...
Symptoms:
-mIRC has bursts of unresponsiveness where nothing happens(cant type or view anything, it's stuck in redraw.
-CPU usage usually saturates during those, with ~50% of kernel usage.
-the symptom usually appears after a few days of heavy use of mirc.(I usually have a largely 3 digit count of windows)
-unloading scripts does not help
-it typically seems to happen when I type
When I check the stack it's never interesting(ie, not stuck in a particular call).
Any ideas?
OS: windows server 2008 64bit
Memory: 4GB of ram(never filled, lots of it free)
CPU: Core 2 Q6600 also mostly idle
