JDK-4244976 : 1.3c1: IE5 on WinNT system will crash if hotspot is used when running the JCK te
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 1999-06-09
  • Updated: 1999-07-13
  • Resolved: 1999-07-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0 betaFixed
Related Reports
Relates :  
Description
The browser will crash if hotspot is used when running the the api tests for the JCK. Note that this problem occurred on NT system that using IE5 to run the JCK
test with trusted mode (I haven't tried on another system yet...)  The same
problem -- browser crash -- with -Xint is on.  This only happens for the api test only (lang and vm have no problem.)

Following is the error when the browser crash:

     Microsoft Visual C++ Library
     iexplore.exe
-------------------------

The problem still exists with Kestrel build J.  

vince.duong@Eng 1999-06-30

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: kestrel-beta INTEGRATED IN: kestrel-beta VERIFIED IN: kestrel kestrel-beta
14-06-2004

EVALUATION vince, with all the changes in the Hotspot and classic VM I believe this bug maybe fixed. Would please try to repro the bug using build-I of Kestrel. Thanks. If the bug still happens let me know and reassign the bug back to me. Thanks mohammad.gharahgouzloo@Eng 1999-06-24 Since Vince has now left the company. I spoke with vijayram manda and he told me that he has been running the JCK API tests and It has worked since build-I. Closing this bug.
24-06-1999