Bug 3791 - core dump in DOMParser.parse() method
Summary: core dump in DOMParser.parse() method
Status: NEW
Alias: None
Product: Xerces-J
Classification: Unclassified
Component: DOM (show other bugs)
Version: 1.4.3
Hardware: HP HP-UX
: P3 blocker
Target Milestone: ---
Assignee: Xerces-J Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-24 04:54 UTC by Manoj
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manoj 2001-09-24 04:54:25 UTC
When nunmer of nodes exceeds 30, DOMParser.parse() method generates coe 
file.But works fine on Windows NT

d dump:

"Signal Dispatcher" daemon prio=9 tid=0xf2778 nid=0x7 runnable [0..0xffffffff]

"Finalizer" daemon prio=9 tid=0xeb490 nid=0x5 waiting on monitor 
[0x5fd6f000..0x5fd6f4e0]
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:112)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)

"Reference Handler" daemon prio=9 tid=0xea7c8 nid=0x4 waiting on monitor 
[0x5fd90000..0x5fd904e0]
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:424)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)

"main" prio=9 tid=0x12680 nid=0x1 runnable [0..0x68281310]

"VM Thread" prio=3 tid=0x73c18 nid=0x3 runnable 

"VM Periodic Task Thread" prio=8 tid=0xf24a0 nid=0x6 waiting on monitor 
#
# Java version:
# HotSpot VM (1.0.1fcs, mixed mode, PA2.0 build 1.2.2.03-00/01/19-PA_RISC2.0)
#
# HotSpot Virtual Machine Error, Unexpected Signal 4
#
# Error ID: 4F533F48500D55580E4350500B22
#
Abort(coredump)
Comment 1 Elena Litani 2001-10-31 14:49:56 UTC
Would you be willing to pick up latest Xerces2 jar (we've just released beta3 
with XML Schema support) and see if the problem still exists?