Saxonica Developer Community

Today

• 
  O'Neil Delpratt SaxonC

  19:17 · Replied in forum

  With some help from valgrind options. The stack trace where things are going wrong in findJavaTZ_md is below:
  ```
  ==4403== 14 bytes in 1 blocks are definitely lost in loss record 1 of 6
  ==4403== at 0x4848899: malloc (in /usr/libe... Saxon/C Help and Discussions: RE: Possible memory leaks

  Hi,
  We're experiencing memory leaks with our application when using SaxonC 12.5.0.
  I believe the attached program demonstrates some of those leaks.
  When running the attached program with valgrind, valgrind reports 17 bytes definitel...
• 
  O'Neil Delpratt Paul Greve wrote in message#9880:
  > Hi O'Neil.
  >
  > One question regarding the loss from the graalvm isolate. Does that loss occur each time a new SaxonProcessor is created? Such that we would want to make our SaxonProcessor a single...

  15:16 · Replied in forum
• 
  O'Neil Delpratt I managed to create a SaxonC debug library which has given a better trace in valgrind.
  First the 288 bytes I am seeing that are possibly lost are to do with the graalvm isolate:
  ```
  ==3224== 288 bytes in 1 blocks are possibly los...

  14:51 · Replied in forum
• 
  O'Neil Delpratt Yes I agree the posts are different. But some how in XSLT the run is triggering the call to `findJavaTZ_md` which I did see in the other post. This is causing the memory leak (14 bytes). I am still investigating it, but it looks like i...

  13:04 · Replied in forum
• 
  O'Neil Delpratt Hi Paul,
  This looks like a duplicate of the discussion here: https://saxonica.plan.io/boards/4/topics/9525

  02:19 · Replied in forum

2025-01-24

• 
  O'Neil Delpratt SaxonC

  19:12 · Replied in forum

  I think the 14 bytes on my code base is lost where we create the. `XsltExecutable`:
  ``` cpp
  xslt = xsltProcessor->compileFromString(styleSheet);
  ```
  Still not sure why, but narrowing it down.
  Saxon/C Help and Discussions: RE: Possible memory leaks

  Hi,
  We're experiencing memory leaks with our application when using SaxonC 12.5.0.
  I believe the attached program demonstrates some of those leaks.
  When running the attached program with valgrind, valgrind reports 17 bytes definitel...
• 
  O'Neil Delpratt In the latest unreleased dev code on SaxonC 12 I am seeing the following:
  ```
  ==567279== LEAK SUMMARY:
  ==567279== definitely lost: 14 bytes in 1 blocks
  ==567279== indirectly lost: 0 bytes in 0 blocks
  ==567279== possibly...

  18:21 · Replied in forum
• 
  O'Neil Delpratt SaxonC

  15:17 · Closed issue

  I have updated the java code to pick up the serialization properties in the SchemaValidator when we call setOutputFile. Bug #6589 (Resolved): Clarify in the documentation where to find serialization parameters

  Following the resolution of bug #6588 it would be good to make the clear in the documentation where the user can find the list of serialization parameters they can use.
• 
  O'Neil Delpratt SaxonC

  10:47 · Closed issue

  Bug fixed in the SchemaValidator class. Bug #6668 (Resolved): SchemaValidator.setOutputFile() does not get applied

  The method `SchemaValidator.setOutputFile()` does not get applied when the `validate` method is called.
  The workaround is to set the output file via the setProperty method:
  ``` cpp
  val->setProperty("o", "filename.xml");
  ```
  
• 
  O'Neil Delpratt The method `SchemaValidator.setOutputFile()` does not get applied when the `validate` method is called.
  The workaround is to set the output file via the setProperty method:
  ``` cpp
  val->setProperty("o", "filename.xml");
  ```
  

  10:46 · Closed issue