Jean-Paul Calderone wrote: > > There's plenty of things other than that one static variable that can get > messed up in this scenario. The access violation could easily come along > with random memory corruption. Fixing just the GC to handle this doesn't > mean your program will be able to keep running correctly. It's difficult > or impossible to know what else has been put into an inconsistent state. > > The real fix is probably to track down what is causing the access > violation. > Once you fix that, the GC shouldn't need to be changed to account for this > possibility, and you'll stop getting dialogs popping up from your app. :) >
Yes I did my job, i had mention it before. but an application would not consist mine only, it could be incorporate your c extension module(s), and others, means problem could be from my side, yours, or others. Though forcing to reset the state would not mean fixing the real problem, but making sure the GC would always try to do its job is important as python itself used as an integrator engine no matter whether it succeed or not. Salam, - Jaimy. -- http://mail.python.org/mailman/listinfo/python-list
