[Tracker-discuss] [issue657] PyGILState_Release FatalError[auto-releasing thread-state, but no thread-state for this thread]

zhaoya metatracker at psf.upfronthosting.co.za
Tue Jul 17 05:05:54 EDT 2018


New submission from zhaoya <zhaoya881010 at 163.com>:

python2.7.15
i have three threads call pythonfuc,and always receive a error "auto-releasing thread-state,but no thread-state for this thread"
log:
2018-07-17T16:03:06+08:00 [INFO] py call function id:11113 1
8208: PyThread_acquire_lock(04AE3E20, 1) called
8208: PyThread_acquire_lock(04AE3E20, 1) -> 1
2018-07-17T16:03:06+08:00 [INFO] py call function id:11112 2
2018-07-17T16:03:06+08:00 [INFO] py call function id:11111 3
threadid:12944,auto-releasing thread-state,but no thread-state for this thread
threadid:11176,auto-releasing thread-state,but no thread-state for this thread
threadid:24708,auto-releasing thread-state,but no thread-state for this thread

code:
threads -->func CallFunction(lpfuncInfo *FuncInfo, arg1 interface{}, arg2, arg3 unsafe.Pointer){
pyGilState := python.PyGILState_Ensure()
......
python.PyGILState_Release(pyGilState)

}

i don't understand,be rather baffling other threads call PyGILState_Release  and threadstates is null.

----------
messages: 3522
nosy: zhaoya881010
priority: bug
status: unread
title: PyGILState_Release FatalError[auto-releasing thread-state,but no thread-state for this thread]

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue657>
_______________________________________________________


More information about the Tracker-discuss mailing list