Closed
Bug 103347
Opened 24 years ago
Closed 24 years ago
Error to getSource crashes the WebClient 1.1
Categories
(Core Graveyard :: Java APIs to WebShell, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jeet_shahani, Assigned: edburns)
References
()
Details
String sou = currentPage.getSource();
A call to the getSource() method causes the webclient to crash. I noted that
the currentPage was not null. This happens on Win98, PC with WebClient1.1
I believe the stack trace is not that helpful.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0xa6e1117
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at org.mozilla.webclient.wrapper_native.NativeEventThread.nativeProcessE
vents(Native Method)
at org.mozilla.webclient.wrapper_native.NativeEventThread.run(NativeEven
tThread.java:244)
Dynamic libraries:
0x7CC00000 - 0x7CC1D000 C:\WINDOWS\SYSTEM\IMAGEHLP.DLL
Local Time = Fri Oct 05 15:14:33 2001
Elapsed Time = 19
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode)
#
# An error report file has been saved as hs_err_pid4294289121.log.
# Please refer to the file for further information.
#
Comment 1•24 years ago
|
||
Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:
1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again
If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•13 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•