Washington Post pages auto refreshes, then crashes

VERIFIED DUPLICATE of bug 40116

Status

P3
critical
VERIFIED DUPLICATE of bug 40116
19 years ago
14 years ago

People

(Reporter: michael_bourgon, Assigned: asa)

Tracking

({crash})

Trunk
x86
All
crash

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
On the Daily 2000051120, I loaded the above URL.  After loading, the page seems
to refresh itself, (it flashes for an instant, then comes up with the exact same
page) then crashes.  I did this twice in a row.  Brought up 2000051120, put in
URL, page loaded, then flashed/refreshed, and crashed.  Hope this helps.

Comment 1

19 years ago
Adding crash keyword
Keywords: crash
(Assignee)

Comment 2

19 years ago
Confirmed with 051308 build under windows 98 and Linux.  upping severity, 
changing OS to all and Setting Status to NEW
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All

Comment 3

19 years ago
I saved the HTML from the page to my own server, and loading the page crashes.  
Nice that they use fully qualified urls in the images.

Then, I removed a lot of content, and it seems that perhaps you need all that 
content to crash (maybe because it takes a little while to redraw).

This might be helpful:  There's a javascript function near the top, with a call 
to it in the <body> tag.

<SCRIPT LANGUAGE="javascript">

<!--
function refreshScreen(){
if (parseInt(navigator.appVersion) >= 4){
        if (navigator.appName == 'Netscape'){
                document.bgColor="#FFFFFF"; document.bgColor="#FFFFFF";
        }
}}
// -->

</SCRIPT>


<BODY ONLOAD="refreshScreen()" ... etc>

If I keep the entire original page from the site, and only remove the two 
document.bgColor statements, I can load and reload the page without crashing.  
Also, it seems that I only have to remove one of the document.bgColor statements 
to keep it from crashing.

The document.bgColor statements cause a refresh of the window.  Maybe the second 
document.bgColor statement causes another refresh while the first refresh is in 
a vulnerable state.

Comment 4

19 years ago
Reproduced on PC/Linux with 5/11 and 5/26 builds. The stack traces are the same
as in bug 40116 "Crash in nsDSURIContentListener::DoContent loading this URL".

*** This bug has been marked as a duplicate of 40116 ***
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE
(Assignee)

Comment 5

19 years ago
Sorry for the spam.  New QA Contact for Browser General.  Thanks for your help
Joseph (good luck with the new job) and welcome aboard Doron Rosenberg
QA Contact: jelwell → doronr

Comment 6

19 years ago
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.