Adam Sikora

I'm getting the same error. `gunicorn==20.1.0`, python `3.8.5`. Increasing the memory for the pod did not help in my case.

Single test to reproduce the issue: ``` import flexmock class A: @classmethod def foo(cls, value: str): return value class B(A): pass def test_foo(): flexmock.flexmock(B).should_receive('foo').and_return('a') B.foo('') flexmock.flexmock(B).should_receive('foo').and_return('b') B.foo('') flexmock._api.flexmock_teardown() flexmock.flexmock(B).should_receive('foo').with_args('a') B.foo('a')...

I have also found out that the issue can be fixed by reversing the order in in which `_reset()` is called on expectations in `flexmock_teardown()`. ``` for expectation in reversed(expectations):...

Here is the output from the container that ran without issues: `gcc -msse3 -dM -E - < /dev/null | egrep "SSE|AVX" | sort` ``` #define __MMX_WITH_SSE__ 1 #define __SSE2_MATH__ 1...

I was able to hit the issue in our containers again and as predicted the CPU flags are the same as the ones posted in previous comment

I was able to get hold of a coredump. This is the backtrace: ``` (gdb) backtrace #0 0x0000000000000000 in ?? () #1 0x00007f5f031e027a in pipeline_forward () from /usr/local/lib/python3.10/dist-packages/blosc2/blosc2_ext.cpython-310-x86_64-linux-gnu.so #2 0x00007f5f031e0700...

No we are for sure running on multi CPU machines as the deployments request 4 CPUs so this will most likely not be related. I'm still not able to reproduce...

I can confirm that the crashes are still happening on the newest `2.6.2` version. Despite my efforts I still don't have an easy way to reproduce the issue. Currently I'm...

Building the `blosc2` Python package from source seems to resolve the issues. We have deployed this workaround to production and we have not seen a single segfault after one week....

Could you perhaps supply such wheel? This way I don't have to test if the crashes still occur in the wheel built by me from master to rule out other...