I didn't have this prob till I put eq2map on auto update.
it happened when I clicked the x(close)
There are so many loops running and thread management going on while eq2map is updating it is possible I've missed stopping some of them when you close eq2map while it isn't totally done it could be trying to access a freed object. So if you close out just at the right time while execution is in the right place you could get this. I'm slowly combing these out.
09-29-2007, 03:00 AM
Threaded Mode
