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
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().
OK, it failed just now even with the “isJVMStarted()” in place on my Ubuntu setup:
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)
The text was updated successfully, but these errors were encountered: