Quote:
Originally Posted by Rogean
[You must be logged in to view images. Log in or Register.]
Heap Corruption with a popup that prevents the batch file from restarting the process because it doesn't fully crash out (main stream keeps running). Kanras and I have spent days worth of time working on going through code from the time it started happening (September - November 2011) checking and rolling back code and haven't found the cause.
Frankly at this point it is the single biggest thing pissing me off, more so than even the latest drama troll scandal.
http://www.rogean.com/images/worldcrash.png
When this happens it just starts spamming connection fails because the UDP Thread of the process is no longer executing, which is also the reason it stops responding to any UDP packets from clients for logging in or zoning. |
Some folks have tossed out band-aid solution ideas and I might as well add to the list while I wait:
I've had an issue where a program would "hard-crash" and pull up th e"this program has stopped responding" window, which is actually some form of the "Doctor Watson" crash handling program.
When that happened, I needed to clear the "this program has stopped responding" window automatically, so I just set up a scheduled task to run "KILL DWWIN.EXE" EVERY minute (or whatever the process was that opened when I got this unwanted pop-up). This way it would completely CLOSE out of the crashed program once the debugger popped up, which would then allow the other scheduled task that tries to run the batch file every minute (as long as that task wasn't already currently running, an option in task scheduler).
Net result is: whenever a crash happens, it closes out of the program automatically, and then the automated scheduled task re-opens my batch file that launches the program.