➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: active_limbo_lock error at program exit
Type: Stage:
Components: Interpreter Core Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gvanrossum Nosy List: anthonybaxter, frangen, gvanrossum
Priority: normal Keywords:

Created on 2001-12-27 19:12 by frangen, last changed 2022-04-10 16:04 by admin. This issue is now closed.

Messages (7)
msg8500 - (view) Author: Simo Salminen (frangen) Date: 2001-12-27 19:12 
I'm running my threaded application, and now and then I get 
following error at exit. I'm using python 2.2 final, but I have had 
the same error with python 2.1. Unfortunately I cannot reproduce 
it. This bug has only occured when I've run the program under 
win2ksp2, tried to produce it under linux but without luck. My 
program is pure python application. I guess saving reference to 
_active_limbo_lock at Thread-class could solve the 
problem..
<error>
Traceback (most recent call last):
  File 
"C:\utils\PYTHON22\lib\threading.py", line 424, in 
__bootstrap
    self.__delete()
  File 
"C:\utils\PYTHON22\lib\threading.py", line 433, in __delete
    
_active_limbo_lock.acquire()
AttributeError: 'NoneType' 
object has no attribute 'acquire'
</error>
msg8501 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2001-12-27 19:51 
Logged In: YES 
user_id=6380

Hm, this looks like it could happen when the treading module
is deleted while there are still threads running. But that
can only happen with daemon threads. Does your program have
daemon threads?
msg8502 - (view) Author: Simo Salminen (frangen) Date: 2001-12-27 22:21 
Logged In: YES 
user_id=291461

Yes, program is running a mainthread and two daemon threads.
msg8503 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2001-12-28 14:35 
Logged In: YES 
user_id=6380

Good.  I saw the same thing in a program, also one using
daemon threads. The daemon threads make this thing
understandable. I'll think of a fix.
msg8504 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2001-12-28 22:07 
Logged In: YES 
user_id=6380

I've checked in a fix that simply ignores the error in this
case: threading.py rev. 1.20.

This is a 2.1.2 and 2.2.1 bugfix candidate!
msg8505 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2002-01-10 12:46 
Logged In: YES 
user_id=29957

checked in to 2.1.2.
msg8506 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2002-01-10 12:49 
Logged In: YES 
user_id=29957

checked in to 2.1.2.
History
Date User Action Args
2022-04-10 16:04:49adminsetgithub: 35837
2001-12-27 19:12:46frangencreate