Closed Bug 255825 Opened 21 years ago Closed 20 years ago

Most pages in true.com will crash Mozilla 1.7.2

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: dd771984842acb296cbde8f8c5a7c161, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040803 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040803 If you log into true.com and 1) take the compatibility test or 2) get the compatible matches at that site, mozilla will consistently crash. Reproducible: Always Steps to Reproduce: 1. go to true.com 2. take the compaibility test, or get compatilibity matches 3. Actual Results: The traceback appears Expected Results: worked
GBR: Could you provide TalkBack incident ID of your crash?
Severity: normal → critical
Keywords: crash
This is also consistent with the site: http://www.kwiksystems.com I have encountered this issue with several sites after upgrading to the Mozilla 1.7.2 on linux RedHat 9 Talkback Incident ID: TB602337Y Prior version 1.7 did not have this behavior. uname -a: Linux test 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Results: Entire window closes, including parent.
TB602337Y is blank.
I tried a couple of things to try to resolve this issue. I think I found where the issue is. Java appears to crash mozilla without any recovery or debug info. Here is what I did: 1. Moved /usr/local/mozilla/plugins/* /tmp/temporary (ie, removed all plugins) 2. Tested site, no errors. 3. Moved all of the plugins back, except java. 4. Tested site, no errors. (asks to install java plugin) 5. Moved java plugin back to plugins directory. 6. Tested site, crash, no logging. Version of java Java(TM) Plug-in 1.4.2_05-b04 File name: libjavaplugin_oji.so Java(TM) Plug-in 1.4.2_05 This is a java issue, a different java version may fix this. Will try to test this next week.
Product: Browser → Seamonkey
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/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.