Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:error': 0.03; 'interpreter': 0.05; 'true,': 0.05; 'subject:Python': 0.06; 'debugging': 0.07; 'error:': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'python': 0.11; 'bug': 0.12; 'thread': 0.14; 'extension,': 0.16; 'received:80.91.229.3': 0.16; 'received:dip0.t-ipconnect.de': 0.16; 'received:plane.gmane.org': 0.16; 'received:t-ipconnect.de': 0.16; 'subject:failed': 0.16; 'fix': 0.17; 'do.': 0.18; 'version.': 0.19; 'command': 0.22; 'header:User-Agent:1': 0.23; 'necessary.': 0.24; 'file.': 0.24; 'looks': 0.24; 'handling': 0.26; 'header:X-Complaints-To:1': 0.27; 'tried': 0.27; 'fixed': 0.29; 'subject:) ': 0.29; 'unix': 0.29; 'related': 0.29; 'code': 0.31; 'crash': 0.31; 'writes:': 0.31; 'run': 0.32; 'running': 0.33; 'implemented': 0.33; 'problem': 0.35; 'problem.': 0.35; 'but': 0.35; 'there': 0.35; 'accessing': 0.36; 'executing': 0.36; 'charset:us-ascii': 0.36; 'should': 0.36; 'error.': 0.37; 'level': 0.37; 'problems': 0.38; 'to:addr:python- list': 0.38; 'issue': 0.38; 'to:addr:python.org': 0.39; 'skip:p 20': 0.39; 'received:org': 0.40; 'commands': 0.60; 'upgrading': 0.60; 'first': 0.61; 'times': 0.62; 'received:217': 0.63; 'different': 0.65; 'results': 0.69; 'caused': 0.69; 'default': 0.69; 'acquiring': 0.84; 'difference.': 0.84; 'hypothesis': 0.84; 'on?': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: dieter Subject: Re: Fatal Python error: PyCOND_WAIT(gil_cond) failed Date: Sat, 13 Dec 2014 08:06:36 +0100 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Gmane-NNTP-Posting-Host: pd9e0a8ef.dip0.t-ipconnect.de User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.22 (linux) Cancel-Lock: sha1:kyCCVJIaQYO2IOp/yb4X+aM6kps= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 34 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1418454416 news.xs4all.nl 2848 [2001:888:2000:d::a6]:51189 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:82473 keepplearningpython writes: > I am running ipython3 on Unix and constantly see this crash - > It happens when i try to issue commands on the ipython interactive shell. > > I have tried to set the PYTHONDIR to /var/tmp/ in case there was an issue accessing the default location of the history file. However, this makes no difference. > > I can run a command a few times successfully after which I hit this error. > ... > Any suggestions on what might be going on? > > > > > Fatal Python error: PyCOND_WAIT(gil_cond) failed Apparently, some thread should wait for the GIL (Python's Global Interpreter Lock) but instead of waiting, the operation results in an error. This looks like an important bug in GIL handling -- likely caused by some C extension, likely executing Python code without first acquiring the GIL. It might be difficult to locate the error: likely C level debugging will be necessary. Should my hypothesis be true, a change in C code would be necessary to fix the problem. I recommend to check for known problems related to GIL handling for all C implemented components of your application. If you are lucky, your problem is known and has been fixed in a different version. Then upgrading would be all you need to do.