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.

Author vstinner
Recipients Arfrever, larry, ned.deily, neologix, pitrou, python-dev, sebastien.renard, serhiy.storchaka, vstinner
Date 2020-03-24.17:01:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585069300.14.0.162988535744.issue20526@roundup.psfhosted.org>
In-reply-to
Content
Just in case, I also ran asyncio_gc.py 10x times on the master branch. I just replaced asyncio.async with asyncio.ensure_future. In short, I consider that the bug is now fixed.


I interrupted the test two times with CTRL+c. 9 runs were stopped correctly. 1 run failed with:

Fatal Python error: _enter_buffered_busy: could not acquire lock for <_io.BufferedWriter name='<stdout>'> at interpreter shutdown, possibly due to daemon threads

But this is a different issue, unrelated to "Modules/gcmodule.c:379: visit_decref: Assertion `((gc)->gc.gc_refs >> (1)) != 0' failed". It's just that the test uses print() in threads, whereas using print() during Python finalization is not reliable. Using os.write() or avoiding print() would avoid the issue.
History
Date User Action Args
2020-03-24 17:01:40vstinnersetrecipients: + vstinner, pitrou, larry, ned.deily, Arfrever, neologix, python-dev, serhiy.storchaka, sebastien.renard
2020-03-24 17:01:40vstinnersetmessageid: <1585069300.14.0.162988535744.issue20526@roundup.psfhosted.org>
2020-03-24 17:01:40vstinnerlinkissue20526 messages
2020-03-24 17:01:39vstinnercreate