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

OK, it failed just now even with the “isJVMStarted()” in place on my Ubuntu setup: #941

Closed
gremmingsy opened this issue Feb 18, 2021 · 0 comments

Comments

@gremmingsy
Copy link

OK, it failed just now even with the “isJVMStarted()” in place on my Ubuntu setup:

Fatal Python error: Segmentation fault

Thread 0x00007fbca3605740 (most recent call first):
  File "/usr/local/lib/python3.8/dist-packages/jpype/_core.py", line 322 in _JTerminate  <<< line number changed because of inserted isJVMStarted().

Again, it must have run without issue several hundred times before this point.

Interestingly, my MacOS-based colleage is regularly seeing what we think is the same issue, and he was able to extract a crash log: hs_err_pid53983.log. This repro is from the cycling of Celery workers, with the SIGSEGV at process exit (or at least we assume so, since it has no discernible effect on the operation of the system). Note: he does not have the inserted isJVMStarted().

Originally posted by @ShaheedHaque in #842 (comment)

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