Closed Bug 250496 Opened 21 years ago Closed 19 years ago

Yet another site specific crash that nukes talkback, though the crash is the more important issue

Categories

(Core Graveyard :: Talkback Client, defect)

Product:
Core Graveyard
Component:
Talkback Client
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 156493

People

(Reporter: xanthian, Assigned: namachi)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040623 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040623 The above URL, when opened with Mozilla, gets at least a screenful of the page displayed, then "bye bye Mozilla" with no error or warning message, and no attempt by talkback (which is otherwise working with this installation on this machine) to pop up and report the error when Mozilla is next invoked. The site also crashes IE 6.0, so whatever problem isn't being handled well isn't particularly Mozilla specific. IE 6.0 does at least manage to put up an error requester as it goes away. Reproducible: Always Steps to Reproduce: 1. Open above URL 2. Goodbye Mozilla Actual Results: Mozilla crashed, repeatably. Expected Results: Survive anything mere data could throw at it. I don't get to see the site long enough to be sure, but it might be trying to bring up a Java applet.
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040705 File name: C:\Programme\Java\jre1.5.0\bin\NPJava32.dll Java Plug-in 1.5.0 for Netscape Navigator (DLL Helper) You are right that an applet is loaded, applet orbit. I´m using 1.5 beta2: http://java.sun.com/j2se/1.5.0/index.jsp
Upgrading from Java JRE 1.4.2 (the most recent stable version) to 1.5.0 (the most recent beta version) removes the crash. This doesn't let Mozilla off the hook, that I can see, since Mozilla is letting itself be crashed by software supposedly running in a defensive "sandbox", but it does confirm the "wfm" from Herman Schwabb. Wiser heads than mine have to decide what to do from this point. xanthian.
Just to bring some closure on the "wfm" issue, I just upgraded to the most recent Mozilla nightly build, and this URL still opens without any longer crashing Mozilla. FWIW. xanthian.
Kent: So should be this bug closed and marked WFM?
> mark bug WORKS FOR ME? No, the bug still exists: Java in a sandbox can take down Mozilla when the Java program throws an error. The subordinate bug still exists: when that severe a crash happens, talkback fails to execute either then or when Mozilla is next executed. That an upgrade of Java makes the Java error go away that _provokes_ the Mozilla erroneous behavior doesn't make _Mozilla_ any less in need of attention, just Java less in need of attention. That website, with Java JRE 1.4.2, provides a repeatable bug which the Mozilla maintainers can use to isolate a critical-level flaw in Mozilla. The golden opportunity shouldn't be lost to find and fix that bug, just because a work-around is available, and the symptoms don't occur when a different Java release is used. That leaves the bug still in the Mozilla code. That is just "sweep the problem under the carpet" thinking. IMAO as a 43-year-experienced programmer, who _loves_ repeatable bugs; the other kind are so much less helpful to isolating problems. xanthian.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Please turn this automated idiocy _off_. I've now received four of these reports in one day about bugs which would long ago have been fixed in a better managed operation. The choice to forget about the bug because no progress has been made in fixing it is <censored>. FWIW xanthian.
the java plugin itself is native code, and can, and often does ask the host to quit. (not crash; quit) if that's what's going on, there's very little mozilla can do. out of process plugins aren't likely to happen before 2010.
Is there a seperate bug number for Talkback failing to launch, this is the closest I could find. Firefox is experienceing _a_lot_ of random crashes and Talkback isn't catching any of them. I'd like to know if thre's a bug for that
*** This bug has been marked as a duplicate of 156493 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.