Saxonica Developer Community

2025-04-11

• 
  O'Neil Delpratt SaxonC

  16:04 · Closed issue

  That particular example actually works on SaxonC 12.6 pre-release with and without the `detach_current_thread`. I was able to reproduce the error on 12.5. The detach_current_thread probably was masking the underlying problem.
  The JVM ... Bug #6743 (Resolved): threading_test.py under Windows 11 and Python 3.12.9 runs the code but then crashes with "Fatal error: StackOverflowError: Enabling the yellow zone.."

  I revisited the sample `threading_test.py` from the pypi/samples directory and found that running it with SaxonC 12.5 HE and Python 3.12.9 under Windows 11 it seems to run through the Python code and output the result files from the XSLT...

2025-04-10

• 
  O'Neil Delpratt SaxonC

  14:17 · Closed issue

  I managed to test SaxonC 12.5 with the new testThreads and it fails. Therefore you will have to wait for 12.6.
  i managed to test 12.6 with the the C++ testThreads on linux and MacOS M1 and it succeeds.
  Support #6740 (Resolved): SaxonC exception

  In the documentation of the SaxonC API there is not much information regarding thread safety.
  My goal is to validate XML with schematrons
  I currently use an XsltExecutable* saved on memory for a long running process because the compila...
• 
  O'Neil Delpratt O'Neil Delpratt wrote in #note-10:
  > Hi,
  >
  > I have finally resolved this issue. The main problem in the internal code was the `SaxonProcessor::attachCurrentThread()` was required before for destroy the processor data from the Object...

  11:11 · Commented on issue
• 
  O'Neil Delpratt Hi,
  I have finally resolved this issue. The main problem in the internal code was the `SaxonProcessor::attachCurrentThread()` was required before for destroy the processor data from the Object Handle's pool.
  The C++ testThreads sam...

  01:35 · Commented on issue

2025-04-08

• 
  O'Neil Delpratt SaxonC

  12:51 · Created issue

  Bug #6745 (New): Saxon-HE: Fatal error: Must either be at a safepoint or in native mode

  Python threading crash reported here https://www.reddit.com/r/javahelp/comments/1bwpia4/saxonhe_fatal_error_must_either_be_at_a_safepoint/

2025-04-07

• 
  O'Neil Delpratt SaxonC

  16:45 · Commented on issue

  I have got further in resolving this issue. The `setInitialMatchSelectionAsFile` is missing the `SaxonProcessor::attachCurrentThread()` required in threaded applications. We are now crashing out in the 3rd thread. Support #6740: SaxonC exception

  In the documentation of the SaxonC API there is not much information regarding thread safety.
  My goal is to validate XML with schematrons
  I currently use an XsltExecutable* saved on memory for a long running process because the compila...
• 
  O'Neil Delpratt Yes I confirm that this sample is still broken. I have reproduced the same error reported by Martin. Currently investigating.

  15:07 · Commented on issue
• 
  O'Neil Delpratt

  10:49 · Edited issue

2025-04-05

• 
  O'Neil Delpratt SaxonC

  15:57 · Commented on issue

  Hi,
  Thanks for creating this issue. Yes we could do more in terms of documentation on threads. I will use this bug issue to track progress on improving the documentation on threads-safety.
  In answer to your question yes the XsltExe... Support #6740: SaxonC exception

  In the documentation of the SaxonC API there is not much information regarding thread safety.
  My goal is to validate XML with schematrons
  I currently use an XsltExecutable* saved on memory for a long running process because the compila...
• 
  O'Neil Delpratt SaxonC

  14:04 · Edited issue

  Bug #6731 (In Progress): applying properties to C Configuration not supported

  In the C API the apply properties to a Processor configuration is not currently supported.