Closed
Bug 384928
Opened 17 years ago
Closed 15 years ago
crash on page load
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: firefox, Unassigned)
References
()
Details
(Keywords: crash, stackwanted, Whiteboard: closeme 2009-07-14)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Open URL Firefox (2.0.0.4 latest) crashes Reproducible: Always Steps to Reproduce: 1. open http://seoblackhat.com/2007/06/10/beating-akismet-with-short-comment-spam/ 2. crash 3. Actual Results: crash Expected Results: page loaded
Comment 1•17 years ago
|
||
Can you get a stacktrace for the crash? See http://kb.mozillazine.org/. Also, if you launch Firefox from the terminal (by just typing "firefox"), what is outputted when you crash?
Keywords: crash,
stackwanted
Version: unspecified → 2.0 Branch
Actually it happens not on the load, but on second zooming in for the text 1. load the page 2. zoom in twice (increase the font size twice) 3. crash console output: bash-3.1# firefox http://seoblackhat.com/2007/06/10/beating-akismet-with-short-comment-spam/ *** e = [Exception... "ServiceManager::GetService returned failure code:" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://browser/content/utilityOverlay.js :: getShellService :: line 294" data: no] The application 'firefox-bin' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. I can't do the stacktrace, I don't how, sorry.
Comment 3•15 years ago
|
||
do you still see this problem using FF 3.5 beta**, or latest update of FF 3.0 started in safe mode***? If yes, please comment If not, please close with resolution set to WORKSFORME. Or INVALID (if problem was extension or the like) ** http://www.mozilla.com/en-US/firefox/all-beta.html *** http://support.mozilla.com/en-US/kb/Safe+Mode
Whiteboard: closeme 2009-07-14
I don't see this problem in Firefox 3.0.11, so it must have been fixed in the meantime.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•