Do you mean the standard Javascript error alerts that pop up when a Javascript error occurs in a browser, or the Windows Messenger Service boxes that can pop up when you receive a message? Or something completely different?
I mean when using xp and a program crashes, there is a MS alert that appears asking if you want to report the error, then automatically closes the program.
I have a program that runs in a browser - tracking my sites, but after several hours it crashes, and I want to know why, and also when the page closes I want a new window to open.
I have placed onunload in the page - but not sure if this will be called if the program crashes (ie)
You can't catch anything in that scenario... it's an error condition that is being handled... and by the time the browser shows the message it's already destroyed your page (ignoring any requests for onunload).
How about switching to another browser and seeing if the problem goes away? As you have mentioned before, the problem is more likely a memory leak with the browser application... it'd be interesting to support/challenge that theory by testing in another browser for a few days.
I think that the error is being triggered because the onreadystatechange event is not being called, making the os think that there is a problem with the browser, but I can't see how I can set a timeout loop around it. any ideas?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.