Currently, mIRC itself can at times lockup from anywhere from a few seconds to a minute or longer, depending on anything from a netsplit on a large network, viewing a large channel log with the built in log viewer, or CPU hungry script(s), for example, a seen script working during a netsplit, or a Hash Table Viewer/Editor, trying to view 15,000 items, in alphabetical order.
This of course can cause mIRC to disconnect from network(s) with a "10053 Software Caused an Abort" error on our end, with a "Ping timeout" or "Connection reset by peer" (what other people would see on the network(s) in the channel(s)), as mIRC seems to be unable to process the ping/pong in order to keep the program connected to the network(s), while processing anything that is CPU intensive.
I am suggesting possibly putting scripts and the internal log viewer into separate threads or cores, to prevent these possible scenarios that I have encountered on occasion.
