-
Bug
-
Resolution: Fixed
-
P3
-
6
-
1.4
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2185506 | 7 | Joe Wang | P3 | Closed | Fixed | m05 |
| JDK-2182527 | 6u18 | Joe Wang | P3 | Resolved | Fixed | b02 |
sjsxp issue 40:
As per StaxTest org.codehaus.stax.test.evt.TestEventReader#testElementText, one
hits an OutOfMemoryError (due to an infinite loop), if:
(a) Event reader has a peeked event, and
(b) XMLEventReader.getElementText() is called
This is because in XMLEventReaderImpl, there's just:
while(event.getEventType() != XMLEvent.END_ELEMENT){
(~ line 175), but nothing to fetch actual next event. Thus, the same (peeked)
event is used over and over again (contents appended to string buffer),
eventually running out of memory.
As per StaxTest org.codehaus.stax.test.evt.TestEventReader#testElementText, one
hits an OutOfMemoryError (due to an infinite loop), if:
(a) Event reader has a peeked event, and
(b) XMLEventReader.getElementText() is called
This is because in XMLEventReaderImpl, there's just:
while(event.getEventType() != XMLEvent.END_ELEMENT){
(~ line 175), but nothing to fetch actual next event. Thus, the same (peeked)
event is used over and over again (contents appended to string buffer),
eventually running out of memory.
- backported by
-
JDK-2182527 sjsxp issue 40: XMLEventReader.getElementText() leads to infinite loop if there's a peeked event
-
- Resolved
-
-
-
- Closed
-