Closed Bug 267260 Opened 20 years ago Closed 20 years ago

Viewing source for bugzilla.mozilla.org will crash Firefox and Seamonkey

Categories

(Core Graveyard :: View Source, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: christopher.vance, Assigned: mrbkap)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041005
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041101 Firefox/1.0RC2

Closing for View Source window which views the HTML source for the Bug List
generated by bugzilla.mozilla.org will cause the browser (Firefox or Mozilla
Seamonkey) to crash.  Talkback does not appear after the crash despite
installing it with the Firefox build.  The same occurs for the Mozilla Suite.

URL given with the report is just an example query.  Any b.m.o query will crash
the browser.

Reproducible: Always
Steps to Reproduce:
1. Visit bugzilla.mozilla.org/query.cgi and search for bugs in any
product/component you wish
2. After the page loads, right-click on the page, select View Page Source from
the context menu, and watch the HTML source load.
3. Close the View Source window any one of the following ways (they all crash
the browser for me, and I can't think of any other way to close the window):
  a) X button in the corner
  b) Double-clicking on the icon in the upper-lefthand corner to close the window
  c) Single-clicking on the icon in the upper-lefthand corner of the View Source
window and selecting Close 
  c) File menu->Close
  d) Ctrl-W
Actual Results:  
The View Source window AND any Firefox (or Seamonkey, if you are using the
suite) browser windows and/or tabs open at the time are closed without warning.

Expected Results:  
The View Source window, and only the View Source window, should have closed.

Occurs in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5)
Gecko/20041005 and Firefox 1.0 RC1 (20041026) as well as the RC2 nightly listed
with the report.

Occurs in existing profiles as well as new profiles created with the newest
nightly -- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Gecko/20041101 Firefox/1.0RC2.

I'll try to get a Talkback crash report with this if I can.
WFM 20041101/trunk/W2K
WFM FF1.0RC1CZ/W2K

Chris: Could you provide TalkBack incident ID?
Keywords: crash
I could not produce a TalkBack ID, despite crashing the 20041005 build of the
Moz Suite several times today.

After uninstalling the Moz suite and installing the 20041102 build of the Suite,
I can no longer reproduce the crash in either Moz or Firefox.  I then
uninstalled and reinstalled the 20041101 FF build I could crash on, and could
not reproduce the crash.

I have been having a few computer problems on my end (today, a bluescreen
"BAD_POOL_CALLER" error) which might be creating a slightly unstable
environment.  The thing is, I could crash with both the Suite and FF with old
and new profiles, after cold and warm boots, and now this no longer happens.

As a note, this also WFM on Linux:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8

Give me till Wednesday evening to sort things out before closing this as WFM.
My OS: WinXP Home, SP2.

On 2nd November 2004, FF 1.0 RC2 was installed [Mozilla/5.0 (Windows; U; Windows
NT 5.1; en-US; rv:1.7.3) Gecko/20041101 Firefox/1.0RC2].  I crashed
mozilla-win32-installer.exe when it was downloaded and subsequently installed from:
 * http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/
 * http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/
 * http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2004-11-02-14-trunk/

There's a decent chance these are all the same builds, as the UA strings are
identical [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5)
Gecko/20041102], but I cannot be positive.

On 2nd November 2004, I uninstalled and installed FF 1.0 RC2 again.  The Mozilla
Suite build from nightly/2004-11-02-14-trunk/ was already installed on the
system.  I crashed firefox-1.0.en-US.win32.installer.exe when (I think) it was
downloaded from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2004-11-01-07-0.11/

I made sure the TalkBack reporting tool was installed in all cases.  At no point
in testing tonight did TalkBack ever appear.

After installing (without logging off or rebooting), the crash happened in all
products.  After warm booting (rebooting), the crash happened in all products. 
After cold booting (turning computer off, then back on), the crash happened in
all products mentioned.  Occured with new profiles, and the crash always
happened in this batch of testing, despite several warm boots and a cold boot at
the end.

The crash happened in FF after the Mozilla Suite was uninstalled.

The crash happens with both the HTTP and HTTPS versions of b.m.o bug queries
such as the URL included with this bug.  I was not logged in when I made these
queries, if it might make a difference.

I have installed FF or the Suite a total of six times tonight.  I cannot think
of anything else to add which might clear things up.

Would someone please reply privately and tell me what I need to do to get
TalkBack to do it's thing in either Mozilla or Firefox? 
http://kb.mozillazine.org/index.phtml?title=Talkback doesn't solve anything.

Help me, Obi Wan.  Adding the QAWANTED keyword.

Would someone running Windows XP, hopefully SP2, try to reproduce this bug with
any of the products mentioned?  Preferably
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2004-11-01-07-0.11/firefox-1.0.en-US.win32.installer.exe
Keywords: qawanted
After posting for assistance in the MozillaZine forums, FYO replied that (s)he
could not reproduce the bug.  I then tried, but I can no longer reproduce the
crash in either the Mozilla Suite or in Firefox.

Closing as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.