Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python 3.13 Fatal Python error: _PyRecursiveMutex_Unlock #2692

Open
onegreyonewhite opened this issue Nov 13, 2024 · 1 comment
Open

Python 3.13 Fatal Python error: _PyRecursiveMutex_Unlock #2692

onegreyonewhite opened this issue Nov 13, 2024 · 1 comment

Comments

@onegreyonewhite
Copy link

onegreyonewhite commented Nov 13, 2024

*** Starting uWSGI 2.0.28 (64bit) on [Wed Nov 13 20:26:32 2024] ***
compiled with version: 10.2.1 20210130 (Red Hat 10.2.1-11) on 31 October 2024 18:21:41
os: Linux-6.8.0-109048-tuxedo #48tux1 SMP PREEMPT_DYNAMIC Sat Oct 26 13:36:26 UTC 2024
nodename: grey-notebook
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 12
current working directory: /home/grey/Projects/vst/quick
writing pidfile to /tmp/quick_web.pid
detected binary path: /home/grey/.pyenv/versions/3.13.0/bin/python3.13
your processes number limit is 255711
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
building mime-types dictionary from file /etc/mime.types...1560 entry found
building mime-types dictionary from file /etc/mime.types...1560 entry found
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 0.0.0.0:8482 fd 3
Python version: 3.13.0 (main, Nov  7 2024, 16:37:26) [GCC 13.2.0]
--- Python VM already initialized ---
Python main interpreter initialized at 0x72c72fb5fa40
python threads support enabled
your server socket listen backlog is limited to 128 connections
your mercy for graceful operations on workers is 60 seconds
mapped 145808 bytes (142 KB) for 1 cores
*** Operational MODE: single process ***
initialized 38 metrics
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 67959)
spawned uWSGI worker 1 (pid: 67960, cores: 1)
metrics collector thread started
Fatal Python error: _PyRecursiveMutex_Unlock: unlocking a recursive mutex that is not owned by the current thread
Python runtime state: initialized

Current thread 0x000072c72fcc5b80 (most recent call first):
  File "/home/grey/Projects/vst-utils/env2/bin/uwsgi", line 8 in <module>

Extension modules: pyuwsgi (total: 1)


DAMN ! worker 1 (pid: 62917) died, killed by signal 6 :( trying respawn ...

Custom worker (for --python-worker-override) - https://github.com/vstconsulting/vstutils/blob/master/vstutils/asgi_worker.py

Same error with clean uwsgi (2.0.28)

Python 3.13 (with gil and without jit).

@onegreyonewhite
Copy link
Author

@xrmx @unbit any updates? --python-worker-override R.I.P. for python 3.13 now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant