Closed Bug 159034 Opened 23 years ago Closed 23 years ago

Applet loads, but then when you recalculate with new info, app hangs

Categories

(Core Graveyard :: Java: OJI, defect)

Product:
Core Graveyard
Component:
Java: OJI
Platform:
x86
Windows ME
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: christinehoff4, Assigned: joe.chou)

References

(
URL
)

Details

Tested on the following: WinME: Netscape 7.0PR1 (1.4.0_01_b03 java) WinME: Netscape 07_23_04_trunk (1.4.0_01_b03 java) Win2000: Netscape 7.0PR1 (1.3.1_02-b02 java) Win98: Netscape 07_23_08_trunk (1.4.0_01-b03 java) WinXP: Netscape 07_11_08_trunk (1.3.1_02-b02 java) Steps to reproduce: 1. Go to: http://www.thomsonfn.com/calculate/RetirementPlan.html 2. Once the applet loads, change the 'age' and click 'Calculate' Expected result: Applet will calculate and graph will reflect new age. Actual result: WinXP, Win2000, Win98: Applet calculates correctly and graph reflects new age. WinME: Applet loads, but when user changes 'age' and clicks 'Calculate', application hangs.
Any update on this?
yup, it loads fine on windows 2k, jre 1.4.0_01 (netscape branch build: 2002-08-22-09-1.0). Let me check on windows XP.
I just checked on Win ME, applet calculates correctly and graph reflects new age. (jre 1.4.0_01, netscape branch build: 2002-08-22-09-1.0)
On comment#2, I said "let me check on winXp, it should be winME". So I couldn't reproduce it. Joe, can you reproduce this?
Let me try it on WinME with an updated build
Tested with the following: WinME with Netscape 08_22_09_1.0.1 (java 1.4.0) WinME with Netscape 08_22_08_1.0.1 (java 1.4.1) Bug reproduced with 1.4.0 java - works fine with 1.4.1 java. Need to find out if we are leaving bugs like this open.
cc: jaworski.
So from what I gather reading this bug report, it appears that the problem doesn't happen with 1.4.1. I'm sorta speaking for the java folks here, but it seems to me that if the problem's cured in a later release, then that's the resolution. Resolving as fixed. If it turns out the same behavior's occuring in a later rev of the jre, feel free to reopen.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Thanks Rob, that was my feeling as well.
QA Contact: pmac → petersen
Verified that problem is fixed with 1.4.1
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.