- Login: mike
- Email: firstname.lastname@example.org
- Registered on: 2012-02-01
- Last connection: 2022-09-28
|Saxon||Manager, Developer, Reporter||2012-02-06|
|W3C QT Specifications||Manager||2019-05-16|
The primary problem I investigated was the heap space problem, this was definitely caused by keeping about 300K XML trees in memory to support the caching of function results. Getting rid of this caching isn't going to make things run fa... Bug #5686: Heap size problems, and crash in TraceListenerProblem reported by email.
To be exact, I have two issues tightly related to each other. First of all I have a transformation (step) where for some element nodes an attribute "variant" must be produced with the help of a function (See...
How large is the serialized output? Does it work if you serialize to a file or to standard output? Is there memory pressure? Have you looked at a heap dump at the point where it hangs?
A StringBuffer uses an underlying char array so... Bug #5697: Serializing Node to String hangsWe are using Saxon-EE 126.96.36.199 on Java and we have a problem serialize an Node to a String.
A transformation on the node is done in 2 minutes. After that, serializing the Node to a String hangs the system.
Her a section of the stacktrac...
I think the "quick fix" is simply to change the code at Expr.js#89 (in my build) from
node === m
(But check for the potential bug identified in comment #9) Bug #5560: intersect doesn’t seem to work correctly for attributesWhile developping XPathle, I stumbled across SaxonJS behaviour that was different than in the Java version.
Consider the commented-out code at https://github.com/gimsieke/xpathle/blob/main/xpathle-lib.xsl#L184
If you use the commen...
I've reviewed the history here in the course of working on the next Saxon 10 maintenance release, and I don't think it's appropriate to make any further changes in this area, so I'm closing the issue. Bug #4839 (Closed): collection(): failed to parse XML fileReported by user on saxon mailing list:
When the collection() feature is used in the XSLT stylesheet. The following error occurs:
collection(): failed to parse XML file file:/D:/Test/sample1.xml: I/O error reported by XML pars...
Closing this in the hope that the version number mismatch is the actual issue. Bug #5096 (Resolved): .NET: FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not foundI'm upgrading Saxon .NET 188.8.131.52 to 10.6. Now, setting the catalog file throws an exception.
Unhandled Exception: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl, saxon-ee-10.6, V...
However, the code introduced by bug #2305 is still present in DotNetPlatform line 496:
The code change applies to the 10.x, 11.x, and 12.x branches even though we have only seen adverse eff...
For 12.x I have implemented a new command-line option -TPxsl:filename which allows you to supply your own stylesheet for formatting the performance profile. This allows you to output the data in XML or JSON, or to display it more selecti... Feature #5613 (Closed): Saxon-EE profiling HTML not well-formedRunning Saxon-EE with "-TP" option for profiling produces a not well-formed HTML document. The element /html/head/meta is not terminated with a closing tag.
I am running Saxon-EE 184.108.40.206 in Oxygen XML Editor 23.1
Also available in: Atom