Simple concept, better handling of mirc crashes.
It is not a very common occurance for mirc to crash, but when it does its often impossible to tell why. Infact half the time it does crash, with no warning, for no apparent reason (under all sorts of circumstances, ie in systray, while actually active and reading something in a window, while in background behind another program and so on). Sometimes windows crash box pops up telling you a debug or whatever is being created, however not at all times.
So i guess my suggestion is better built in crash handling, ie create a crash.log with as much information as possible. Many programs incorporate such features, which greatly helps in determining exactly what caused the crash.
Personally, i have been unable to determine any constants in the situations, apart from actually being connected to multiple servers. Have also been unable to find anything in any of my script files that could be causing crashes.
I do not recall ever experiencing crashes pre mirc 6.x and not sure even about 6.0, and my system/background processes and so on have not changed since before they started.
As i said, they are not common occurances, but some better crash handling would definately help pin point the causes.
