Saxon

Hi Michael,

I am using the API as follows:

In our ContetInfo.cs, we reference the Saxon.Api .dll

The following objects are created:

private Processor processor;

   private XsltCompiler compiler;


    //this stores xslt files in memory and redues calls from file system

    //private static Dictionary<string, XsltTransformer> _loadedXsltFiles;

   private static Dictionary<string, XsltExecuProcessor> _loadedXsltProcessor;

The Constructor for ContentInfo

The _loadedXsltProcessor is a Dictionary, key value is the name of the xslt as string and the Value, is the XsltExecuProcessor object, which is an object that contains the XsltExecutable object and Processor object as below:

I am storing the complied xslt as an XsltExecutable and the Processor used in the Dictionary so that it can be reused, using the xslt FilePath I check if there is an existing XsltExecutable and Processor and reuse them, If not the create the XsltExecutable and Processor, complie the xslt and sort in the Dictonary as below:

From the ConvertXml method

Please let me know if I have implemented the API incorrectly, and could the Dictionary be causing the memory usage problem?

I am investigating this.

Kind Regards

Ashona

From: Saxonica Developer Community [mailto:dropbox+saxonica+f38e@plan.io]

Sent: Tuesday, March 24, 2015 12:12 PM

Subject: [Saxon - Support #2337] Saxon 9-6.0 .net api, excessive memory usage

Have you made any progress in collecting more information on this?

There's another thread on high memory usage in Saxon on .NET at https://saxonica.plan.io/issues/2339, does this yield any insights?

We can't really make any progress unless we have more information on what your application is doing. A memory dump that shows what objects are occupying the space would be very useful as a way forward.

Our request for further information elicited no response, so I am closing the ticket.