Closed
Bug 360121
Opened 19 years ago
Closed 18 years ago
The link http://www.dallasnews.com/business/ consistently crashes Firefox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: txjdhicks, Unassigned)
References
()
Details
(Keywords: crash, Whiteboard: CLOSEME 07/14)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)
The link http://www.dallasnews.com/business/ consistently crashes Firefox
To be complete, I am using the following extensions:
Adblock 0.5.3.043
Beagle Indexer 0.5
Google Toolbar for Firefox 2.1.20060807L
Master Password Timeout 0.2.5
Reproducible: Always
Steps to Reproduce:
1. Go to the link http://www.dallasnews.com/business/
2.
3.
Actual Results:
Firefox crashes
Expected Results:
See the page correctly. So far it is the only page on the dallasnews.com site that crashes Firefox.
Does the following page crash? If yes, it's a Java problem. If not, there's some Flash too...
Also, please paste a stack from talkback (regardless of whose problem it is) - see http://kb.mozillazine.org/Talkback for how. That of course will require a Mozilla.org/com build, so please use that. We can't do much with Ubuntu builds...
http://www.dallasnews.com/sharedcontent/dws/includes/business/stockgroup_ticker_stocks.htm
Other things you can do: Try disabling extensions (in particular Adblock) before trying again; it might be interacting badly with plugins.
Comment 2•18 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2 and the latest Java? If not, can you please close this bug as WORKSFORME. Thanks!
Severity: normal → critical
Keywords: crash
Whiteboard: CLOSEME 07/14
Version: unspecified → 2.0 Branch
![]() |
||
Comment 3•18 years ago
|
||
No reply → resolving WORKSFORME.
If the bug is present in the newest versions, please reopen. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•