Thanks for the response.
I just wanted to be sure that this situation was being noticed and acted upon. I was pretty upset by the way some folks ignored it on another forum and just acted like it was a non-issue, then got all huffy when I took them to task for it. This is happening to a lot more people than some people want to believe, but some of us will speak up and some won't. A poll would be a nice idea, but again some will vote and some won't. I operate on the premise that if the programmers don't know about the bugs, they can't possibly fix them, and the more they know about them, the easier it is to isolate them. Of course, I've been programming since 1975, so I do have a little bit of experience.
I'm basing my observation on the frequency of this occurence on what I'm reading on at least three different forums where I'm seeing amazingly similar complaints that center around an error message that comes back to the operating system saying that mIRC can't read memory at some specific location and that error crashes mIRC. The error is always associated with a DCC chat session or fserve session, which uses the same mechanism.
