You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you running a service? I can't say I'm too familiar with the file you uploaded, but the file contains a few things that lead me to believe you may be. As David said, it would be helpful to know what you were doing.
tb220 commented on Mar 25, 2010
tb220mannequin
MannequinAuthor
More actions
The application consists of three processes: Process A provides a web interface to the remote user and watchdog services for process B, which A creates by using the multiprocessing module. Process B does the real work and provides a GUI to the local user. Process A communicates with process B via the xmlrpclib module. Both A and B are python processes. Process B uses the subprocess module to start process C, which is not a python process, and it communicates with it using the xmlrpclib module. Process B is the one that crashes every now and then when sys.exit is invoked.
I will try to produce the smallest possible application I can that still suffers from the problem and I will upload it.
serwy commented on Jul 15, 2012
serwymannequin
Mannequin
More actions
tb220, is this still a bug? Python 2.6 is now in security-fix-only mode.
Activity
tb220 commentedon Mar 25, 2010
Attached the error report generated by Windows. The problem occurs in 1 out of 10 shutdowns.
tb220 commentedon Mar 25, 2010
Please let me know how I can provide you with additional information.
bitdancer commentedon Mar 25, 2010
A recipe for reproducing the problem would be the most useful thing. I suspect the windows error report is pretty much useless in this context.
briancurtin commentedon Mar 25, 2010
Are you running a service? I can't say I'm too familiar with the file you uploaded, but the file contains a few things that lead me to believe you may be. As David said, it would be helpful to know what you were doing.
tb220 commentedon Mar 25, 2010
The application consists of three processes: Process A provides a web interface to the remote user and watchdog services for process B, which A creates by using the multiprocessing module. Process B does the real work and provides a GUI to the local user. Process A communicates with process B via the xmlrpclib module. Both A and B are python processes. Process B uses the subprocess module to start process C, which is not a python process, and it communicates with it using the xmlrpclib module. Process B is the one that crashes every now and then when sys.exit is invoked.
I will try to produce the smallest possible application I can that still suffers from the problem and I will upload it.
serwy commentedon Jul 15, 2012
tb220, is this still a bug? Python 2.6 is now in security-fix-only mode.
birkenfeld commentedon Oct 13, 2013
Closing due to lack of feedback.