Closed Bug 298030 Opened 20 years ago Closed 19 years ago

Visiting URL causes immediate crash http://www.imaging-resource.com/PRODS/LS4K/L40A.HTM

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: rich, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2)

Visiting the following URl causes immediate crash:
http://www.imaging-resource.com/PRODS/LS4K/L40A.HTM


Reproducible: Always

Steps to Reproduce:
1. Visit URL http://www.imaging-resource.com/PRODS/LS4K/L40A.HTM
2. Browser crashes.


Actual Results:  
Browser crashes.

Expected Results:  
Displayed the page.
wfm, nightly firefox Trunk on OS X Tiger.

Possibly a flash issue?
I should clarify that I've also got three extensions installed which
might well affect things:

* User-agent switcher 0.6.6
* Web-developer 0.9.3
* Flashblock 1.3.1.1

User-agent switcher is very stable, but the other two could well be
causing the problem.
fwiw, i'm using Adblock and Web Developer myself without problems. 

Can you try with a clean profile/without extensions?
Can you provide a Talkback ID?
As comment#4 suggests:
We need a Talkback ID from an original Mozilla.org build. We don't accept Debian
based bug reports because they add their own patches (and Talkback is only in
Mozilla.org builds availible)
It would be also nice if you use a nightly trunk build because The Gecko in
FF1.0.4 is over 12 months old.
 
Keywords: crash
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.