[Bug 58486] JreMemoryLeakPreventionListener: initialize two further JRE classes

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=58486

--- Comment #5 from Luke Woodward  ---
I have a bug number for the report now: JDK-8146961.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 58486] JreMemoryLeakPreventionListener: initialize two further JRE classes

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=58486

--- Comment #4 from Luke Woodward  ---
(In reply to Konstantin Kolinko from comment #3)
> I raised this issue with Apache Xerces,
> https://issues.apache.org/jira/browse/XERCESJ-1667
> 
> 
> (In reply to Luke Woodward from comment #0)
> > 
> > I have filed a bug report with Oracle to change the behaviour of these two
> > classes.  However, until this gets fixed (if it gets fixed at all), it would
> > be appreciated if the JreMemoryLeakPreventionListener could be adapted to
> > handle these two classes.
> 
> Do you have a bug number for your report?

No, I don't.  I have a Review ID, JI-9025281, but that's all I've heard from
Oracle so far.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 58486] JreMemoryLeakPreventionListener: initialize two further JRE classes

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=58486

Mark Thomas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Mark Thomas  ---
Fixed in trunk, 8.0.x (for 8.0.29) and 7.0.x (for 7.0.66).

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 58486] JreMemoryLeakPreventionListener: initialize two further JRE classes

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=58486

--- Comment #3 from Konstantin Kolinko  ---
I raised this issue with Apache Xerces,
https://issues.apache.org/jira/browse/XERCESJ-1667


(In reply to Luke Woodward from comment #0)
> 
> I have filed a bug report with Oracle to change the behaviour of these two
> classes.  However, until this gets fixed (if it gets fixed at all), it would
> be appreciated if the JreMemoryLeakPreventionListener could be adapted to
> handle these two classes.

Do you have a bug number for your report?

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 58486] JreMemoryLeakPreventionListener: initialize two further JRE classes

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=58486

Luke Woodward  changed:

   What|Removed |Added

 OS||All

--- Comment #1 from Luke Woodward  ---
The servlet in my previous comment demonstrates a leak with the 'abort'
exception in the class
com.sun.org.apache.xml.internal.serialize.DOMSerializerImpl.  If you replace
the lines

document.createElement("test");
DOMImplementationLS implementation =
(DOMImplementationLS)document.getImplementation();
implementation.createLSSerializer().writeToString(document);

with

document.normalizeDocument();

then this causes a leak with
com.sun.org.apache.xerces.internal.dom.DOMNormalizer.abort instead.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org