Shane Harvey added the comment:
This issue was resolved in https://jira.mongodb.org/browse/PYTHON-2621
The cause of the segfault was determined to be gevent 1.3.4 (2018) and/or
greenlet 0.4.13 (2018). When the reporter upgraded to gevent==21.1.2 and
greenlet==1.0 the segfault went away.
---
STINNER Victor added the comment:
> That makes me think that this is a problem in pymongo module. I will report
> this bug to them.
Yeah, in 90% of cases, the bug comes from a third party C extensions. That's
why Python 3.10 now dumps the list of 3rd party C extensions on a fatal error
:-)
Abraham Macias added the comment:
Thank you Victor for your response.
I follow your advice but the output was an error in a different point of the
code and I couldn't see any information about memory allocations.
But, I compiled Python 3.7 from source and modified the "Python/errors.c" code
STINNER Victor added the comment:
> What can be happening? How can I help to debug this?
Try to run your application in the Python Debug Mode:
https://docs.python.org/dev/library/devmode.html
The best is if you can run your application with a Python built in debug mode.
Usually, it's a bug
New submission from Abraham Macias :
Hi, I'm dealing with random crashes when using pymongo in Python 3.7.3 in a
Debian Buster.
This is the python backtrace:
(gdb) thread apply all py-bt
Thread 2 (Thread 0x7f9817d95700 (LWP 221)):
Traceback (most recent call first):
File "/usr/local/lib/pyt
