You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We had been running django with gunicorn + gevent and started seeing a number of segfaults that caused 139 errors. This happened with django running inside a docker container with alpine and
python 3.12.3
greenlet 3.0.1
but stopped happening with
python 3.12.5
greenlet 3.0.3
we have no clue how and why, and have no way to reproduce it even if we did try a lot.
Here is a screenshot of gdb showing the (potentially) relevant stacktrace, obtained from a coredump (based on work from @jazzido)
The text was updated successfully, but these errors were encountered:
Hi,
We had been running django with gunicorn + gevent and started seeing a number of segfaults that caused 139 errors. This happened with django running inside a docker container with alpine and
but stopped happening with
we have no clue how and why, and have no way to reproduce it even if we did try a lot.
Here is a screenshot of gdb showing the (potentially) relevant stacktrace, obtained from a coredump (based on work from @jazzido)
The text was updated successfully, but these errors were encountered: