Bug #4520
closedJET RUNTIME HAS DETECTED UNRECOVERABLE ERROR: system exception at 0x0000000101a1bf56
100%
Description
The following error was reported by user in the Saxon forum post: https://saxonica.plan.io/boards/3/topics/7810
*JET RUNTIME HAS DETECTED UNRECOVERABLE ERROR: system exception at 0x0000000101a1bf56 Please, contact the vendor of the application. Core dump will be written to "/cores/core.2821" (max size 4294967295 kB). To ensure a full core dump, try "ulimit -c unlimited" Extra information about error is saved in the "jet_err_2821.txt" file.
Fatal Error: another attempt of termination from the same thread. *
In the log file we see the following message:
Signal 11 (SIGSEGV)
siginfo: si_signo 11, si_errno 0, si_code 0, si_addr 0x0000000000000000
The following python script was used to reproduce the error:
import saxonc
with saxonc.PySaxonProcessor(license=False) as proc:
print("Test Python")
print(proc.version)
xp = proc.new_xpath_processor()
'''try: '''
xp.declare_namespace("xmlns:xsi", "http://www.w3.org/2001/XMLSchema-instance")
xp.declare_namespace("", "urn:hl7-org:v3")
xp.set_context(file_name="doc.xml")
xPath = """//recordTarget[number(substring(patientRole/patient/birthTime/@value,1,4)) < 2015]/patientRole/patient/birthTime/@value"""
results = xp.evaluate(xPath
Updated by O'Neil Delpratt over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Details of the fix has been added in the forum post 7810. In summary the file SaxonProcessor.cpp incorrectly uses NewGlobalRef/DeleteGlobalRef in the Constructor and Destructor of the SaxonProcessor class. The removal of these calls to the jni functions has been removed on the development branch.
Updated by O'Neil Delpratt over 4 years ago
- Status changed from Resolved to In Progress
The following article gives example of the use of the NewGlobalRef:
http://journals.ecs.soton.ac.uk/java/tutorial/native1.1/implementing/refs.html
Updated by O'Neil Delpratt almost 2 years ago
- Status changed from In Progress to Closed
- Fixed in version set to 11.1
I am closing this bug as no further action needed. If problem still exists please reopen issue.
Please register to edit this issue