mIRC 6.12 crashes due to page file error - 30/11/03 01:02 PM
I am having a recurring problem with mIRC crashing. I've seen this problem with other people, too. In all cases, the error message consistently includes the bold text in the following error message:
Unhandled exception at 0x0042cbe4 in mirc_upp.exe: 0xC0000005:
Access violation reading location 0x032934e8.
I happen to be using UPP, so I reported the bug first on that forum and got the following reply:
"ah yes 0x0042cbe4. it's a bug in mirc actually. mirc doesn't check the requested memory so if your paging file has errors things could go wrong."
It seems to be connected to people exiting the fileserver or dcc chat by typing exit or by clicking the X. One of the others had it happen frequently. I wasn't seeing it that often, but the frequency seems to be increasing.
Is there any way that mIRC could possibly be modified to check the memory without a major modification? Is there anything that we can do to ensure that our page file does not have any errors in it? Since I'm not the only one who is having this error and since it is really a problem, is there any possibilty of getting a fix for this any time soon?
If others are seeing this problem, please speak up in here so Khaled will know.
Unhandled exception at 0x0042cbe4 in mirc_upp.exe: 0xC0000005:
Access violation reading location 0x032934e8.
I happen to be using UPP, so I reported the bug first on that forum and got the following reply:
"ah yes 0x0042cbe4. it's a bug in mirc actually. mirc doesn't check the requested memory so if your paging file has errors things could go wrong."
It seems to be connected to people exiting the fileserver or dcc chat by typing exit or by clicking the X. One of the others had it happen frequently. I wasn't seeing it that often, but the frequency seems to be increasing.
Is there any way that mIRC could possibly be modified to check the memory without a major modification? Is there anything that we can do to ensure that our page file does not have any errors in it? Since I'm not the only one who is having this error and since it is really a problem, is there any possibilty of getting a fix for this any time soon?
If others are seeing this problem, please speak up in here so Khaled will know.