Saxon

Hi Bob,

Thanks for reporting back to us the problem you are having. It is an interesting problem that we would like to explore further.

Firstly, the StaticError could be genuinely gathering errors in your stylesheet which are not failure errors, but just warnings. It would be good to inspect your stylesheet. Is it possible that you could send us your code, privately or on this bug issue?

Secondly, it would be good to eliminate the bytecode generation feature from this, which might be the cause of the high memory usage, please could you switch it off and run your program again to see if the issue goes away.

If you are running Saxon from the commandline just add the following option:

--generateByteCode:off

If you are running Saxon from C# code the following code. (I assume you have a processor object):

Processor processor = new Processor(true);
processor.SetProperty("http://saxon.sf.net/feature/generateByteCode", "false");

In Saxon 9.6 we have moved to the latest IKVM, which has better garbage collection for the object created using the bytecode generation feature for .NET. We have also made some improvements. It might be worth evaluating the latest release if my suggestions above fail to solve your problem.

It is possible that the bottle neck is somewhere else. Could you please send us some more details of the memory dump?

Hi:

Attached, please fin the style sheets, DTD'S and a C# class we use to compile the xslt.

We are currently already turning off the byte code.

I will try to get more info on the memory dump.

Hi,

sorry for the delay in getting back to you. I am trying to create a repo with the C# code and stylesheets you sent last week, but it seems like I need some other libraries to run your code. Specifically I am not sure where to find WKHMR.

Hi,

Glad to know that you have sorted out your memory issues in your XSLT. Therefore I am closing this bug issue as won't fix.

Any other problems please let us know.