Closed Bug 428284 Opened 18 years ago Closed 15 years ago

crash with google reader opened and switching the url to gmail

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: miguel.ventura, Unassigned)

Details

(Keywords: crash, stackwanted)

Attachments

(3 files)

Output from WinDbg lm command
14.78 KB, text/plain
Details
Output from WinDbg kp and kP commands
6.14 KB, text/plain
Details
Output from WinDbg "!heap -v" command
6.08 KB, text/plain
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 the Crash Reporter didn't popup but I have windbg configured to attach automatically. Still it didn't give me much info. Reproducible: Couldn't Reproduce This is my session in windbg. If you need more information, I saved the dumpfile so let me know. This seems to be something in memory management. I had enough free memory at the time the program crashed. 0:000> kP n # ChildEBP RetAddr 00 0012ed64 7c90e9ab ntdll!KiFastSystemCallRet 01 0012ed68 7c86372c ntdll!ZwWaitForMultipleObjects+0xc 02 0012f4d4 7c8436da kernel32!UnhandledExceptionFilter+0x8e4 03 0012f4dc 7c839b09 kernel32!BaseProcessStart+0x39 04 0012f504 7c9037bf kernel32!_except_handler3+0x61 05 0012f528 7c90378b ntdll!ExecuteHandler2+0x26 06 0012f5d8 7c90eafa ntdll!ExecuteHandler+0x24 07 0012f5d8 60006672 ntdll!KiUserExceptionDispatcher+0xe WARNING: Stack unwind information not available. Following frames may be wrong. 08 0012f8d8 60006913 MOZCRT19!_realloc_crt+0x1da2 09 0012f8f0 60006972 MOZCRT19!_realloc_crt+0x2043 0a 00000000 00000000 MOZCRT19!_realloc_crt+0x20a2 0:000> ~* . 0 Id: 41c.49c Suspend: 1 Teb: 7ffdf000 Unfrozen Start: firefox+0x15a0 (004015a0) Priority: 0 Priority class: 32 Affinity: 3 1 Id: 41c.878 Suspend: 1 Teb: 7ffde000 Unfrozen Start: xul!gfxASurface::SurfaceDestroyFunc+0x8ed (6064efc8) Priority: 0 Priority class: 32 Affinity: 3 2 Id: 41c.8dc Suspend: 1 Teb: 7ffdd000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 3 Id: 41c.f80 Suspend: 1 Teb: 7ffda000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 4 Id: 41c.f94 Suspend: 1 Teb: 7ffd9000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 5 Id: 41c.f98 Suspend: 1 Teb: 7ffd7000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 6 Id: 41c.fac Suspend: 1 Teb: 7ffaf000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 7 Id: 41c.fb0 Suspend: 1 Teb: 7ffae000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 8 Id: 41c.53c Suspend: 1 Teb: 7ffac000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 9 Id: 41c.160 Suspend: 1 Teb: 7ffd6000 Unfrozen Start: NPSWF32!native_ShockwaveFlash_TCallLabel+0x3ed36 (30102c90) Priority: 0 Priority class: 32 Affinity: 3 10 Id: 41c.d60 Suspend: 1 Teb: 7ffaa000 Unfrozen Start: NPSWF32!native_ShockwaveFlash_TCallLabel+0x3ed36 (30102c90) Priority: 0 Priority class: 32 Affinity: 3 11 Id: 41c.544 Suspend: 1 Teb: 7ffa9000 Unfrozen Start: wdmaud!MixerCallbackThread (72d230e8) Priority: 15 Priority class: 32 Affinity: 3 12 Id: 41c.fe8 Suspend: 1 Teb: 7ffa8000 Unfrozen Start: WINMM!timeThread (76b5aee7) Priority: 15 Priority class: 32 Affinity: 3 13 Id: 41c.74c Suspend: 1 Teb: 7ffab000 Unfrozen Start: ntdll!RtlpTimerThread (7c92798d) Priority: 0 Priority class: 32 Affinity: 3 14 Id: 41c.f9c Suspend: 1 Teb: 7ffdb000 Unfrozen Start: WINMM!mciwindow (76b44dd6) Priority: 2 Priority class: 32 Affinity: 3 15 Id: 41c.adc Suspend: 1 Teb: 7ffd5000 Unfrozen Start: 001724da Priority: 0 Priority class: 32 Affinity: 3 16 Id: 41c.1710 Suspend: 1 Teb: 7ffd4000 Unfrozen Start: mswsock!SockAsyncThread (71a5d5af) Priority: 1 Priority class: 32 Affinity: 3 17 Id: 41c.164c Suspend: 1 Teb: 7ffad000 Unfrozen Start: 001724dc Priority: 0 Priority class: 32 Affinity: 3 18 Id: 41c.bfc Suspend: 1 Teb: 7ffa7000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 19 Id: 41c.ab8 Suspend: 1 Teb: 7ffd8000 Unfrozen Start: MOZCRT19!endthreadex+0xa0 (60002c60) Priority: 0 Priority class: 32 Affinity: 3 20 Id: 41c.84c Suspend: 1 Teb: 7ffa6000 Unfrozen Start: ole32!CRpcThreadCache::RpcWorkerThreadEntry (774fe429) Priority: 0 Priority class: 32 Affinity: 3 21 Id: 41c.116c Suspend: 1 Teb: 7ffa5000 Unfrozen Priority: 0 Priority class: 32 Affinity: 3
Do you have disabled the extension.compatibility check or do you use some unusual plugin in about:plugins (besides flash, quicktime, wmp) ?
Extension compatibility check is enabled. Enabled addons were: download statusbar, downthemall!, firebug, google notebook, pdf download, personas, prism, remember the milk for gmail, stylish, web developer As for plugins, I've got the usual shockwave flash, adobe acrobat, WPF, Java6, VLC, WMP and MS DRM.
you need to setup sympath, see: http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg please *attach* the output from: lm .reload /f kp and also attach the output from about:plugins typically this is caused by ypState
URL: -
Keywords: crash, stackwanted
ok .hh !heap (i.e. read the docs) try this: (if it doesn't work, figure out how to make it work) !heap -v when you get useful output, attach it. please try disabling (i.e. uninstalling) tortoise. historically it has been poorly written. do you have any accessibility agents installed?
Assignee: nobody → aaronleventhal
Component: General → Disability Access APIs
Product: Firefox → Core
QA Contact: general → accessibility-apis
Version: unspecified → Trunk
Is the crash still occurring in nightly builds? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Sorry for providing the outputs one by one, but I'm really not used to windbg and I don't really know which information is the most useful for you! Also: no accessibility agents installed, except for the stuff that already comes in a default XP install (like MS Narrator) which are all disabled.
do you use dom inspector? if so, try disabling it.
In Windows, we usually only turn on accessibility if we receive a WM_GETOBJECT message from somewhere, or if accessibility is being turned on via Chrome JS, like in DOM Inspector. Software that usually sends this message wants to interact with us through MSAA (Microsoft Active Accessibility). Typically these are screen readers for the visually impaired. Do you use the Microsoft lense feature, for example? Or on a different tangent: Does Firebug maybe turn on accessibility features?
There used to be an addon called about:accessibilityenabled which would tell you if it was on.
Comment 1 shows shockwave flash. I think it's probably related to that.
@Aaron: I can't know if it still crashes on the nightlies because I can't find a deterministic way to reproduce the crash on the very same version. @Zehe: No MS Lens nor narrator. However your firebug tip seems good. I usually have firebug disabled but, if I enable it on some site and go to the HTML tree tab, I get the following error on the console: Permission denied to get property XULElement.accessibleType XPCSafeJSObjectWrapper.cpp (line 445) I really can't remember if it was enabled or disabled at the time. As I said, I usually have it disabled, but as I had the browser open for a while...
Ok... enabling Firebug (I'm using http://www.getfirebug.com/releases/firebug/1.1/firebug-1.1.0b12.xpi), navigating to a page, enabling it and inspecting some HTML element does increase the probability of crash. I've already managed to crash firefox twice now by doing that procedure on some tab and then opening gmail and google reader and closing their tabs randomly. The stacktrace is the same. By the way... shouldn't the crash reporter pop up with these crashes?
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Can anybody to reproduce it in Firefox 4?
I had these crashes in 3.0 while it was beta, but didn't get them anymore after that (which includes Firefox 4). Currently using Mozilla/5.0 (Windows NT 6.0; WOW64; rv:2.0b13pre) Gecko/20110309 Firefox/4.0b13pre ID:20110309030420
Thanks Miguel.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
See comment #17.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: