Closed Bug 476350 Opened 17 years ago Closed 17 years ago

Crash (@0xXXXX93f8, first 4 digits vary) upon logging out of Gmail

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: netrolller.3d, Unassigned)

References

(
URL
)

Details

I've recently started experiencing crashes when logging out of Gmail on Windows 7 beta 1. The stack signature does not lead anywhere, but the stack itself has some distinctive frames that are always identical. Here are some dumps: http://crash-stats.mozilla.com/report/index/8a11e3e5-287d-45b1-90ac-a59e92090201 http://crash-stats.mozilla.com/report/index/db3f7e67-fa5e-42ba-9478-56bca2090201 http://crash-stats.mozilla.com/report/index/ce48c5ea-cc31-458a-a464-eff5d2090201 http://crash-stats.mozilla.com/report/index/07b2f889-270c-4eaf-9e21-3d7b12090131 http://crash-stats.mozilla.com/report/index/d7c0eb70-a28a-413f-a5b3-f9f5d2090131 http://crash-stats.mozilla.com/report/index/e65e1b0d-fd46-472e-ac39-d66e12090130 http://crash-stats.mozilla.com/report/index/0dedeab0-ff58-4a07-b004-83a8a2090127 Visual C++ Express 2008 lists 4 User32 stack frames (as opposed to 3 in the dumps, but the dumps are from Firefox 3.1b2, while I debugged Seamonkey 2.0a1pre), with the following symbol names: user32.dll!_InternalCallWinProc@20() + 0x23 bytes user32.dll!_UserCallWinProcCheckWow@32() + 0xb3 bytes user32.dll!_DispatchMessageWorker@8() + 0xe6 bytes user32.dll!_DispatchMessageW@4() + 0xf bytes
Severity: normal → critical
Do you have some addons with binary components installed like Google Toolbar or Google gears ?
No, it happens with a freshly-compiled Seamonkey build as well. (AFAIK Seamonkey does not inherit Firefox's extensions.) I do have Google Chrome installed, however.
Which flash player is installed because Gmail is using flash for playing the sound notification ?
AFAIK Flash Player 10 is installed. I'll check.
Apparently it was the Google Talk Plugin that was not playing nice with Firefox 3.1. Disabling it helped. (P.S.: Maybe Safe Mode should also disable all plugins - that would save a lot of headache.)
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.