I'm evaluating the Saxon ee 18.104.22.168 (.net) version and trying to compare its performance between 32 bit & 64 bit environments. In the past we faced memory problems and decided to evaluate 64 bit environment as a solution. I have a test application using the .Net interface provided since eventually we will be using the Saxon .Net API in our application. I get the following error when running it in the 64 bit server although it works fine in the 32 bit server --
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at net.sf.saxon.event.Sender.sendPullSource(PullSource , Receiver , ParseOptions )
at net.sf.saxon.event.Sender.send(Source source, Receiver receiver, ParseOptions options)
at net.sf.saxon.Configuration.buildDocument(Source source, ParseOptions parseOptions)
at net.sf.saxon.Configuration.buildDocument(Source source)
at Saxon.Api.DocumentBuilder.Build(XmlReader reader)
at ForsTestApp.Form1.ExecuteSaxonStreamMode(String xml, String xslt, String result) in E:\BMD_Workarea\ForsPerf\ForsTestApp\Form1.cs:line 792
Following is the code snippet
XmlReader xslReader = null;
XmlReader xmlReader = null;
XsltCompiler c = null;
xslReader = XmlReader.Create(xsltfilenname);
Processor p = new Processor();
DocumentBuilder docB = p.NewDocumentBuilder();
docB.BaseUri = new Uri("urn:test");
xmlReader = XmlReader.Create(xmlfilename);
XdmNode rootNode = docB.Build(xmlReader);
c = p.NewXsltCompiler();
c.ErrorList = new ArrayList();
c.BaseUri = new Uri("urn:test");
XsltExecutable executable = c.Compile(xslReader);
XsltTransformer transof = executable.Load();
transof.InitialTemplate = new QName("", "", "main");
transof.InitialContextNode = rootNode;
Serializer serializer = new Serializer();
serializer.SetOutputFile(resultfilename); //for file
// Transform the source XML to System.out.
Please let me know a resolution for this.
NOTICE: If received in error, please destroy, and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. We may monitor and store emails to the extent permitted by applicable law.