You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nokogiri installs a XML error handler, this handler keeps a list of warning/errors.
Each warning or error is internally represented as a org.xml.sax.SAXParseException.
These are than available as (transformed) XML errors using doc.errors ...
Growing the error list is tied to the document but is not bounded -> many (failing) transformations will cause the list to grow. This could lead to potential memory leaks.
We need a few reproducers for filling the error list - potentially one during parsing and also verify whether the list could potentially grow during transformation or xpath extraction.
A reasonable resolution for the issue would be to introduce a configuration for parse options to allow an XML document to be created in strict mode - in this mode exceptions bubble up (instead of being stored). The plugin should than potentially log the errors and tag the event with a parse failure ...
The text was updated successfully, but these errors were encountered:
Nokogiri installs a XML error handler, this handler keeps a list of warning/errors.
Each warning or error is internally represented as a
org.xml.sax.SAXParseException
.These are than available as (transformed) XML errors using
doc.errors
...Growing the error list is tied to the document but is not bounded -> many (failing) transformations will cause the list to grow. This could lead to potential memory leaks.
We need a few reproducers for filling the error list - potentially one during parsing and also verify whether the list could potentially grow during transformation or xpath extraction.
A reasonable resolution for the issue would be to introduce a configuration for parse options to allow an XML document to be created in strict mode - in this mode exceptions bubble up (instead of being stored). The plugin should than potentially log the errors and tag the event with a parse failure ...
The text was updated successfully, but these errors were encountered: