Forums Feature Suggestions netsplit flood

I noticed that when mass netplits and rejoins occurs in mirc chan windows, they can last for quite a long time, during which not only the cpu is used at 100%, which can cause other applications to freeze and stop, but it can also stops and timeout all file transfers via mirc.
So it'd be very more safe if mirc could have an option to prevent those kind of flood in chan mssg, for instance by detecting the number of consecutives lines with the words "quit" and "join" .

I've been in 1000+ user channels, where a netsplit occurred causing more than 500 people to quit and rejoin, I experienced no 100% CPU usage. Are you on an old machine? Ie., if you are on a 200mhz machine, that would certainly explain this...

He he .. I have an old machine Celeron 333 192 ram ..
All office aplication work fine .. (Office 2000, Mozilla, Winamp, The Bat,Vb)
And mIRC work perfect .. But when is netsplit .. Or some flood the channel with change of the nicks .. The mIRC Gui dead completetly (CPU 100%) ..
mIRC have some command to stop display that ? (Disconnect ? )

What is the requirement of mIRC ?

I also have this problem with mIRC 6.03 and netsplits (Windows XP Professional, XP 2000+, 512MB DDR PC2700).

well thanks for ur suggestion but in fact im running under winxp sp1 with an athlon xp+2200 and 1go ddr 2700, so i dont believe its due to my hardware oldness ...

Well I'm running WinXP SP1a with a 1.4Ghz Athlon TBird, I also have another machine that is a 350Mhz Pentium II, and another that is a Athlon XP 3000+, and I've never experienced this problem on any of the machines.

xp 3k? hmm--time for a hardware upgrade for me >:D

actually, the 3200+ just came out

Yes, but how pricy >:\

Cheapest I found was $463

I'm on a 2.4 ghz P4 with 512mb DDR, and my computer will freeze for a few seconds sometimes on netsplits or just mass joining.

Sometimes it does, sometimes it doesn't. So, I don't know what the problem is exactly.

I have many scripts that use "on join" and "on part" events. Perhaps all of that parsing is what causes the pause.

too rush for my blood...

It just splitted and this time it didn't freeze like it use to do, very odd.