79131 - webclient exit crash

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Java APIs to WebShell, defect)

Description

[sameer thakur]

The bug is always reproducible; I use windows binary distribution of 
webclient 1.0 and netscape 6,
    if u use sample application supplied with webclient distribution and click 
on DOMViewer and after that click couple of time on text in  browser window and 
then exit the application it will exit with following
    warning in console and a popup window.

    ==> NSPR:EventReceiver:java.exe -Application Error
            _____, memory could not be read.

    in console window

========== rv:0  node:8a81a8========== rv:0  node:8a81a8========== 
rv:0  node:8a
59dc========== rv:0  node:8a59dc========== rv:0  
node:9674208========== rv:0  no
de:9674208Got windowClosing
Destroying the BrowserControl
ImplObjectNative.delete()
ImplObjectNative.delete()
ImplObjectNative.delete()
ImplObjectNative.delete()
#
# An EXCEPTION_ACCESS_VIOLATION exception has been detected in 
native code outside the VM.
# Program counter=0x1
#


    I narrowed down the problem in following code in DOMViewerFrame.java in test 
example

    ==> eventTarget.addEventListener("click", this, false); // add listener to 
the DOMDocument

    it will always crash the webclient if we register the listener to the 
document,
    i feel this is due the problem in shutdown process of the webclient code in 
jni thread part because i observed that on exiting code after shutting down all 
the processes code will again try to start webclient  resulting in memory 
location not found error.

Comment 1

[geetha.vaidyanaathan]

changing QA contact
Alexei , can you contact netscape/bugzilla folks again to make sure that
the QA contact is changed to you for Webclient for all future bugs.


-Geetha

Comment 2

[Jeet Shahani]

I was using jre 1.3.0_01.

Comment 3

[edburns]

a.  Known bug.

Comment 4

[Ed Suominen]

Attachment: Error Dialog screen shot

Comment 5

[Robert Kaiser]

This bug has no info about current software versions, please file a new bug for new issues or reopen this one with current info, including a crash signature if it still happens.