Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

bindings docs: the Ctrl-C known issue links jpype#1496 and documents the SIGTERM crash (jpype#1497) - #200

Merged
tae898 merged 1 commit into
mainfrom
docs-jpype-links
Oct 6, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs-jpype-links

Conversation

@tae898

@tae898 tae898 commented Oct 6, 2026

Copy link
Copy Markdown

Links the two JPype issues the user filed (jpype-project/jpype#1496, the SIGINT ordering race, and ArcadeData#1497, the SIGTERM crash) from the Ctrl-C known-issues entry, and documents the SIGTERM crash with the workaround as measured: a handler registered after the JVM has started stops the process at once; one registered before it avoids the crash but runs only when the main thread next executes Python code.

Closes #199.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ubz3m6QXHESerCkehC1qgi

…the SIGTERM crash (jpype#1497) with its workaround

With startJVM(interrupt=False) and no Python SIGTERM handler, kill -TERM crashes the process in PyErr_SetInterruptEx (exit -6; 10 of 10 on JPype 1.7.1 and master, 3 of 3 through the bindings). A handler registered after the first database is opened stops it at once (3 of 3); one registered before the JVM starts avoids the crash but runs only when the main thread next executes Python code, so a blocking time.sleep delays it (measured with plain JPype).

Closes #199.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ubz3m6QXHESerCkehC1qgi
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: known-issues links the JPype issues for the Ctrl-C race and documents the SIGTERM crash

1 participant