A fair amount of the 0x0 crashes listed here: http://dbaron.org/log/20090922-crashes-data/interesting-modules-windows have the Quicktime plugin. We don't have good stacks from the crash server yet so the only way to find these crashes is to unwind manually. The stack looks something like this: 0 0x0 eip = 0x00000000 esp = 0x0012f29c ebp = 0x6170706c ebx = 0x00000000 esi = 0x0800b5fe edi = 0x000001f1 eax = 0x00040002 ecx = 0x07fa4ff0 edx = 0x07ff67e0 efl = 0x00010286 1 QuickTime.qts + 0x1c22d6 eip = 0x669c22d7 esp = 0x0012f2a0 ebp = 0x6170706c 2 QuickTime.qts + 0x98225 eip = 0x66898226 esp = 0x0012f2d0 ebp = 0x6170706c 3 QuickTime.qts + 0x1c1f2f eip = 0x669c1f30 esp = 0x0012f2f0 ebp = 0x6170706c 4 QuickTime.qts + 0x11b2af eip = 0x6691b2b0 esp = 0x0012f308 ebp = 0x6170706c 5 QuickTimeWebHelper.qtx + 0x9f3c eip = 0x675a9f3d esp = 0x0012f318 ebp = 0x6170706c 6 xul.dll!nsCOMPtr_base::~nsCOMPtr_base() [nsCOMPtr.cpp:c6f51c76fb5d : 81 + 0x7] eip = 0x100b502e esp = 0x0012f334 ebp = 0x6170706c 7 xul.dll!nsPluginInstanceOwner::GetMode(nsPluginMode *) [nsObjectFrame.cpp:c6f51c76fb5d : 2362 + 0xf] eip = 0x10699db7 esp = 0x0012f33c ebp = 0x6170706c 8 xul.dll!nsNPAPIPluginInstance::InitializePlugin(nsIPluginInstancePeer *) [nsNPAPIPluginInstance.cpp:c6f51c76fb5d : 1030 + 0x4f] eip = 0x1070c805 esp = 0x0012f34c ebp = 0x6170706c

My 10.6 lab machine hit this crash - http://crash-stats.mozilla.com/report/index/bp-d72383a5-7a8a-469f-bd1a-188d52100105 is the report. Will try to see if I can get a set of STR.

Got this bug linked by a crash today: http://crash-stats.mozilla.com/report/index/bp-2ce96a0c-a81b-43d6-94ce-c24292101228 I don't seem to have quicktime anywhere.

Yeah, @0x0 is a pretty generic signature. It just means that something tried to execute code at a NULL address, and our stack walking code couldn't find any of the calling frames.

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.