Closed Bug 254532 Opened 22 years ago Closed 20 years ago

Browser Crashes for specific URL

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kolberg_dev, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040731 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040731 Browser Crashes when attempting to access http://www.fix.law-firm.co.uk/ Need to confirm that it's not just my build and that it is in effect for others. Reproducible: Always Steps to Reproduce: 1.Access site 2.Browser goes poof 3. Actual Results: Browser crashes with no errors Expected Results: Displayed webpage
WFM 20040804 PC/WinXP
Assignee: nobody → general
Severity: normal → critical
Component: Layout: HTML Frames → Browser-General
Keywords: crash
QA Contact: core.layout.html-frames → general
Kal: Could you provide TalkBack incident ID?
WFM Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.1+ There's Java on the right-hand frame. Maybe Java crashed your browser?
I'm uncertain how to provide the talkback, since mozilla is just dying or was just dying without error message, sorry. But if the page has Java on it that is likely my problem as I haven't quite been able to integrate mozilla and java yet. If no one else is getting the error, I would figure it's just my build and set about rebuilding it rather than having everyone chasing shadows.
*** Bug 255522 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Kal Kolberg: Could you reproduce this crash using Mozilla 1.8 beta 1?
do you have java installed? what version? do you have it properly installed (symlinked, not copied)? if you open Mozilla from a terminal and visit the page, does it print any messages in the terminal?
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.