Saxonica Developer Community

2023-09-27

• 
  O'Neil Delpratt SaxonC

  18:32 · Commented on issue

  Hi,
  I ran the PHPUnit test with my patched code and it ran without the seg fault. But some of the php scripts are throwing seg fault. Bug #6197: PHP - SIGSEGV in zend_mm_alloc_small or in Java_java_lang_ProcessEnvironment_environ

  Hi there,
  I am trying to use Saxon to run XSLT transformations from PHP. I am encountering systematic crashes when using the PHP extension with code that exercises PHP's autoloading features or is more than a trivial example script (C...

2023-09-25

• 
  O'Neil Delpratt SaxonC

  12:00 · Edited issue

  Thanks for providing the container. I will take a look at it.
  Current progress: I have added some object reference counting for the memory management of the \Saxon\SaxonProcessor object. No longer getting the segmentation fault, but P... Bug #6197 (In Progress): PHP - SIGSEGV in zend_mm_alloc_small or in Java_java_lang_ProcessEnvironment_environ

  Hi there,
  I am trying to use Saxon to run XSLT transformations from PHP. I am encountering systematic crashes when using the PHP extension with code that exercises PHP's autoloading features or is more than a trivial example script (C...

2023-09-21

• 
  O'Neil Delpratt SaxonC

  00:41 · Commented on issue

  I ran the example in the initial bug entry to reproduce the error. I think it was running with Symfony because code: `$r = new Symfony\Component\HttpFoundation\Response();` would not work otherwise. I then modified the code with the setu... Bug #6197: PHP - SIGSEGV in zend_mm_alloc_small or in Java_java_lang_ProcessEnvironment_environ

  Hi there,
  I am trying to use Saxon to run XSLT transformations from PHP. I am encountering systematic crashes when using the PHP extension with code that exercises PHP's autoloading features or is more than a trivial example script (C...

2023-09-20

• 
  O'Neil Delpratt SaxonC

  14:03 · Commented on issue

  Hi,
  I managed to reproduce the segmentation fault running with Symfony on my linux box. It is indeed a SaxonC bug.
  The reassigning of the created SaxonProcessor object is causing a GC action on the SaxonProcessor, which the exten... Bug #6197: PHP - SIGSEGV in zend_mm_alloc_small or in Java_java_lang_ProcessEnvironment_environ

  Hi there,
  I am trying to use Saxon to run XSLT transformations from PHP. I am encountering systematic crashes when using the PHP extension with code that exercises PHP's autoloading features or is more than a trivial example script (C...

2023-09-19

• 
  O'Neil Delpratt SaxonC

  19:09 · Commented on issue

  I have applied a patch to this encoding issue.
  The encoding of the output is handled by the property on the Java Serialiser class (i.e. `set_property('!encoding', 'UTF-8')`). However for the input string the user can now specify the en... Bug #6182: UTF-8 in string based C API functions

  I tried to get the following code running and the encoding of the return value seems off.
  ``` cpp
  void testUTF8StringTemplate(SaxonProcessor *proc, Xslt30Processor *trans,
  sResultCount *sresult) {
  const...

2023-09-14

• 
  O'Neil Delpratt SaxonC

  08:01 · Closed issue

  Bug fixed in testValidator.cpp and updated documentation of *SchemaValidator.setSourceNode()* Bug #6195 (Resolved): Sources node objects not deleted in the C++ Schema validation samples

  Reported by user in the forum post https://saxonica.plan.io/boards/4/topics/9525
  Some of the C++ Schema Validation samples in testValidator.cpp we are not deleting the created source node objects at
  the end of the test run. if not d...
• 
  O'Neil Delpratt Reported by user in the forum post https://saxonica.plan.io/boards/4/topics/9525
  Some of the C++ Schema Validation samples in testValidator.cpp we are not deleting the created source node objects at
  the end of the test run. if not d...

  07:45 · Closed issue
• 
  O'Neil Delpratt SaxonC

  07:46 · Replied in forum

  Thanks for the observation of the node object in the sample program. I will fix the samples accordingly that don't have a delete. Apologies if this caused a confusion. I have created the bug issue #6195 to track its progress. Saxon/C Help and Discussions: RE: Possible memory leak in SchemaValidator class

  We're using Saxonc-eec-12.2 for the ARMv8 on linux to do schema validation of XML source docs.
  There appears to be a memory leak in the SchemaValidator class, more specfically when calling the registerSchemaFromFile function.
  Attache...

2023-09-13

• 
  O'Neil Delpratt SaxonC

  11:52 · Replied in forum

  Running valgrind with options --leak-check=full --show-leak-kinds=all gives some clue where the 14 bytes are lost:
  ```
  ==158520== 14 bytes in 1 blocks are definitely lost in loss record 1 of 5
  ==158520== at 0x4848899: malloc (in ... Saxon/C Help and Discussions: RE: Possible memory leak in SchemaValidator class

  We're using Saxonc-eec-12.2 for the ARMv8 on linux to do schema validation of XML source docs.
  There appears to be a memory leak in the SchemaValidator class, more specfically when calling the registerSchemaFromFile function.
  Attache...
• 
  O'Neil Delpratt I managed to run the repo using valgrind with iteration=2. See the leak summary:
  ```
  ==158361== LEAK SUMMARY:
  ==158361== definitely lost: 350 bytes in 3 blocks
  ==158361== indirectly lost: 0 bytes in 0 blocks
  ==158361== ...

  11:48 · Replied in forum