Closed Bug 82176 Opened 24 years ago Closed 24 years ago

NetGenesis applet causes browser to lock up, become unworkable [REQUESTOR: NetGenesis]

Categories

(Core Graveyard :: Java: OJI, defect, P1)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: drapeau, Assigned: joe.chou)

References

()

Details

Net Genesis has an applet that, when run in the Netscape 6 or Mozilla browsers, causes the browser's UI to become unresponsive. There is currently no external test case for this applet yet; the URL listed in this bug is Sun-internal, and is available only to Sun employees for now. This applet also fails on Solaris, but for a different reason: the applet hard-codes the usage of the "Arial" font, which is available on Windows but not on Solaris. The applet doesn't gracefull handle the error. In any case, that is a different problem (not an OJI bug), and I mention it here to point out that this bug is specifically filed against Windows.
Marking as one of the OJI group's hot bugs.
Whiteboard: [oji_escalation]
Summary: NetGenesis applet causes browser to lock up, become unworkable → NetGenesis applet causes browser to lock up, become unworkable [REQUESTOR: NetGenesis]
Visiting the applet doesn't cause the browser hang. Leaving the page causes this exception: java.lang.IllegalStateException: Can't dispose InputContext while it's active at sun.awt.im.InputContext.dispose(Unknown Source) at java.awt.Window$1$DisposeAction.run(Unknown Source) at java.awt.Window.dispose(Unknown Source) at sun.plugin.navig.win32.PluginFrame.windowClosing (PluginFrame.java:121) at java.awt.Window.processWindowEvent(Unknown Source) at java.awt.Window.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Which causes the browser to hang.
Status: NEW → ASSIGNED
p1
Priority: -- → P1
Adding status to indicate actively being worked on by Ed right now.
Whiteboard: [oji_escalation] → [oji_escalation] oji_working
Asked for insight from Stanley.
After determining that this bug is in the Java side, I've opened bugtraq bug 4464761. Re-assigning to Jim Melvin.
Assignee: edburns → James.Melvin
Status: ASSIGNED → NEW
Whiteboard: [oji_escalation] oji_working → [oji_escalation]
Removing status keyword since the bug is not an OJI escalation anymore (it's in Java Plug-In).
Whiteboard: [oji_escalation]
I believe the bug is on the Java side because it appears that some necessary mechanism for removing the java implemented PluginFrame from its InputContext doesn't appear to be happening. The exception happens because the InputContext's currentClient component is not null: public void dispose() { if (currentClientComponent != null) { throw new IllegalStateException("Can't dispose InputContext while it's active"); } Ed
eric.hawkes@eng.sun.com closed the bugtraq bug 4464761 as not-reproducible with 1.4. The hang sounds like 4411534, which I could not reproduce in 1.4. eric.hawkes@eng 2001-06-15 Talked to Zhengyu.Gu@sun.com (the responsible engineer). He can't reproduce this with 1.4 either. I'll close this as not reproducible. If the bug is escalated, someone can reopen this report. eric.hawkes@eng 2001-06-15
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
SPAM: reassigning OJI bugs to new QA, pmac. (227 bugs)
QA Contact: shrir → pmac
Chris Petersen is a new QA contact for oji component. His email is: petersen@netscape.com
Assignee: James.Melvin → petersen
fixing small error for pmac@netscape.com (filter with : SPAMMAILSUCKS)
Assignee: petersen → joe.chou
QA Contact: pmac → petersen
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.