|
Quick Lists
|
|
Bug ID:
|
4672707
|
|
Votes
|
1
|
|
Synopsis
|
Applet lifecycle shutdown sequences causes IE browser hang on page switch:PIT09
|
|
Category
|
java_plugin:iexplorer
|
|
Reported Against
|
hopper
|
|
Release Fixed
|
1.4.2(mantis)
|
|
State
|
10-Fix Delivered,
Verified,
bug
|
|
Priority:
|
1-Very High
|
|
Related Bugs
|
4523285
|
|
Submit Date
|
23-APR-2002
|
|
Description
|
Platform : Win32
Browser : IE
Hopper Build :/net/sqesvr/deployment3/hopper/JPI-PIT-08/Build02/win32.PIT08-2
Applet lifecycle shutdown sequences is not consistent on Internet Explorer.
1) Install JRE
2) Invoke IE browser
3) Go to the following Test case
http://j2se.east/%7Ezg131198/lifecycle_test/index.html
4) switch the pages, or even open new browser windows from menu.
Expected Behavior
-----------------
Only when all browser windows of the browser instance has been closed, "Destroy" Java dialog will popup.
Current behavior
----------------
1.) Expected Behavior is not consistent on IE browser
2.) When switched between the pages using Browsers Back/Forward button causes IE to hang
3.)Any dialogs / windows popped up in the applets destroy method are hidden in the background and are not shown to the user for his response, which could cause confusion as browser is hanging.
Note : It works fine with NS browsers
|
|
Work Around
|
N/A
|
|
Evaluation
|
The problem is deadlock.
xxxxx@xxxxx 2002-05-03
We are de-committing this for hopper-beta and committing this to Mantis.
We will have to document the restriction against GUI components displayed
from the stop() or destroy() methods.
xxxxx@xxxxx 2002-05-07
The putback mainly fixed legacy lifecycle inconsistent problem. When there is a legacy lifecycle applet on the latest instance of the browser, during the shutdown, it could hang the browser.
There are still problems related to page switch with normal and legacy life cycle applets. The problem will be further addressed with 4678577.
xxxxx@xxxxx 2002-07-22
|
|
Comments
|
Submitted On 11-MAY-2003
dont_fuk_wit_the_boy
centralstationrecords.com.au
Submitted On 26-AUG-2004
thomas.gr
The problem still exists in 1.4.2-b28
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |