Author vstinner
Recipients iwienand, mcepl, pitrou, serhiy.storchaka, vstinner, vzhestkov, yselivanov
Date 2021-08-04.15:32:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1628091125.03.0.710185252453.issue31426@roundup.psfhosted.org>
In-reply-to
Content
This bug report mentions Python 3.5 and 3.6 which no longer accept bugfixes. Since nobody reported issues on Python 3.9 and newer (which still accept bugfixes), I close the issue as out of date.

Victor Zhestkov:
> It seems I have the same segfault, but with 3.6.13 python shipped with SLE15SP2. It's salt-api process under intensive usage. I'm able to reproduce it, but can't isolate due to the service complexity. In some cases it takes about 5 minutes to be crashed, but in others it could run with no crash for about an hour or more (I keep the workload on this service with a kind of stress test).

See my notes to debug crashes happening during GC collections:
https://pythondev.readthedocs.io/debug_tools.html#debug-crash-in-garbage-collection-visit-decref

You can try to use a way smaller GC threshold: call gc.set_threshold(5) at the very beginning of your application.

I strongly advice you to use a debug mode of Python, since it includes way more debug modes.

I also strongly advice you to upgrade Python. I added many debug checks for object consistency in the GC in recent Python releases (3.8, 3.9, 3.10) and when a bug arises, Python dumps way more information about the faulty Python object.

Good luck for debug it. But please don't comment this closed issue. Python 3.6 is no longer supported.
History
Date User Action Args
2021-08-04 15:32:05vstinnersetrecipients: + vstinner, pitrou, mcepl, iwienand, serhiy.storchaka, yselivanov, vzhestkov
2021-08-04 15:32:05vstinnersetmessageid: <1628091125.03.0.710185252453.issue31426@roundup.psfhosted.org>
2021-08-04 15:32:05vstinnerlinkissue31426 messages
2021-08-04 15:32:04vstinnercreate