Closed Bug 440726 Opened 17 years ago Closed 17 years ago

Crash after unlocking system

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED WONTFIX

People

(Reporter: maxcantor, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 I left a Firefox window open on my office computer overnight. When I came back in the morning, unlocked my computer, and tried to check my Gmail, it crashed. I think it crashed after I typed "gmail" and when I hit Ctrl + Alt + Enter (to complete the .com URI and launch in another tab), but it MAY have crashed before then. about:crashes is blank, so this was not caught by the crash handler. When I restarted Firefox, it detected that it had crashed, and successfully recovered my tabs. Reproducible: Couldn't Reproduce Steps to Reproduce: ??? Sorry! No idea how to reproduce. I did transcribe the following information from the Windows crash report: appver: 1.9.0.3071 ModName: mozcrt19.dll ModVer: 8.0.0.0 Offset: 00006c6c I'm using the default theme, and the following extensions are installed: All-in-One Gestures DownThemAll! Favicon Picker 2 Firebug Google Gears Greasemonkey Live HTTP Headers Nuke Anything Enhanced Web Developer It occurs to me that I installed All-in-One Gestures despite that it isn't specifically compatible with FF3 yet, so this crash may have resulted from its presence, though I wasn't doing anything that involved its functionality when Firefox crashed. If, from the information above, you can tell that it does result from this out-of-date extension, feel free to remove this bug report. Here is my build configuration: Build platform target i686-pc-mingw32 Build tools Compiler Version Compiler flags cl 14.00.50727.762 -GL -wd4624 -wd4952 -TC -nologo -W3 -Gy -Fd$(PDBFILE) cl 14.00.50727.762 -GR- -GL -wd4624 -wd4952 -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE) Configure arguments --enable-application=browser --enable-update-channel=release --enable-optimize --disable-debug --disable-tests --enable-update-packaging --enable-official-branding --enable-jemalloc --with-crashreporter-enable-percent=25
For a crash you have to send a crash report with the mozilla crashreporter, type about:crashes in Firefox as URL and post the crash id in the bug report. >mozcrt19.dll This is up to 95% either an incompatible addon with binary component or you use a tablet PC. We need the crahs id to be sure.
@Matthias: Please read my initial description more thoroughly. about:crashes is empty, as Firefox did not detect the crash before closing. However, if mozcrt19.dll indicates addon problems, then it's probably All-in-One Gestures. If someone can confirm this, this crash report can be closed.
If you can reproduce this kind of crash then follow the injstructions at http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg to get a stack trace. Nobody can be sure without seeing a full stack trace but a crash in >mozcrt19.dll is usually froom an out-of-date .dll. Is All-in-One Gestures coming with a binary component (dll) then I'm sure that the addon caused this. Did you override the system version check of that addon ?
@Mattias: I did. I don't know if All-in-One Gestures comes with a binary component, but ever since I disabled it there have been no crashes, so it sounds like that's what caused the crash. I'm closing this ticket--sorry for clogging the DB with cruft! :-)
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Please don't report bug about addons that you only can use because you modified the version strings. Download the XPI Installation file instead of installing it, rename *.xpi to *.zip and watch the contents in the Zip file. All extensions that are coming with a binary component can crash the browser and you should never override the version check of such Addons.
Status: RESOLVED → VERIFIED
Sorry--when it crashed, I had forgotten that I overrode the version check. Like I said, sorry for clogging the bug database!
You need to log in before you can comment on or make changes to this bug.