Closed Bug 434752 Opened 16 years ago Closed 15 years ago

figure out which extensions are causing crashes [@arena_dalloc_small]

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: chofmann, Unassigned)

References

Details

(Keywords: crash, Whiteboard: cloud, next)

Crash Data

split off from bug 420678 so we can identify plugins or extensions that might need to get blocklisted
I currently have the following extensions installed:

Adblock Plus 0.7.5.4
Deutsches Wörterbuch 1.0.1
Gmail Notifier 0.6.3.3

I also looked for and deleted rests of previously installed extensions, so those are really the only extensions in my profile directory.

In addition I have the following plugins enabled:
Shockwave Flash 10.0 b218
RealPlayer Enterprise(tm) LiveConnect-Enabled Plug-In
Java Plug-in 1.6.0_05 for Netscape Navigator (DLL Helper) - different .dll files
Npdsplay dll

I saw the last arena_dalloc_small crash last night: http://crash-stats.mozilla.com/report/index/9165e461-2626-11dd-8025-001321b13766

Okay, I also discovered random crashes [@arena_dalloc_small]. 
I have the following add-ons installed:

BugMeNot 1.8
ChatZilla 0.9.82.1
DownThemAll 1.0.1
Fasterfox 2.0.1
IE Tab 1.5.20080310

Additionally these are the plugins I have installed:
* Adobe Acrobat
* IE Tab Plugin
* Java(TM) Platform SE 6.0 U5
* Mozilla Default Plugin
* Shockwave Flash 9.0r115
* Silverlight Plugin 1.0.30401.0
* VLC Multimedia Plugin Version 0.8.6f
* Windows Presentation Foundation
* Yahoo Application State Plugin (but deactivated)
The same crashes on me whenever there is both AJAX and Flash in play, sometimes as much as every 10 minutes. Check my crash report just posted:

http://crash-stats.mozilla.com/report/index/c378340c-2c12-11dd-84d4-001cc45a2ce4?p=1

Signature:	arena_dalloc_small
UUID:		c378340c-2c12-11dd-84d4-001cc45a2ce4
Time:		2008-05-27 10:31:24-07:00
Uptime:		894
Product:	Firefox
Version:	3.1a1pre
Build ID:	2008052703
OS:		Windows NT
OS Version:	6.0.6000
CPU:		x86
CPU Info:	GenuineIntel family 6 model 15 stepping 2
Crash Reason:	EXCEPTION_ACCESS_VIOLATION
Crash Address:	0x42340008
I'm on 3.1a1pre, no extensions whatsoever, and crashing all the time as well. I'm sure this cannot be an isolated case, as googling about this hits several who are also having this problem.
Are you using any accessibility tools, or are you on a Tablet PC? If so, please follow along on bug 436375.
No, I'm on an HP Pavilion laptop. Vista Ultimate. Dual Centrino. About 1 year old in technology (32 bit).
I think I now found out which extension is causing the crash: It must be ChatZilla. Using Chatzilla Firefox crashes more often esp. while fetching channels. 
(In reply to comment #6)
> Are you using any accessibility tools, or are you on a Tablet PC? 

I indeed have a tablet and the Input Panel is running on it. Seems like at least one of my recent arena_dalloc_small crashes is indeed related to accessibility.


oh, right, the input panel. i knew it was used somewhere. thanks!

http://msdn.microsoft.com/en-us/library/ms818403.aspx
http://msdn.microsoft.com/en-us/library/ms811573.aspx
Severity: normal → critical
Component: Extension Compatibility → Disability Access APIs
Keywords: crash
Product: Firefox → Core
QA Contact: extension.compatibility → accessibility-apis
Version: unspecified → Trunk
timeless: we're working on the tablet pc crash over in bug 436375. I'd say leave this bug alone.

*shrug* find me someone who doesn't have a tablet pc (input panel) :)
sounds like bug 430826 is one of the plugin crashes that can/should be blocked
Depends on: 430826
Status?  Did this one just go away?
still ranks between #7 and #14 on firefox 3.1b2.  

https://wiki.mozilla.org/QA/Topcrashes#Current_topcrashes_being_tracked_3.1b2

some research is needed to dig out which plugins might be a part of the current problem.
Chris, what about Firefox 3.1b3pre? I know it will be used by only a small range of users but what state the bug has there?
no crashes in the last week for 3.1.b3pre builds but as you say, I think the pool of users and plugins running on those builds is too small to get a good idea on how we are doing.   We should leave this bug open and re-check a few days after 3.1b3 is released.
looks like this signature is definitely still out there.

on average users seem to hit the crash 134.571 (minutes) since last crash 

distribution of versions where the crash was found on 20090817
 534 Firefox 3.5.2
 132 Firefox 3.0.13
 102 Firefox 3.0
  32 Firefox 3.5.1
  22 Firefox 3.5
  17 Firefox 3.0.11
  13 Firefox 3.0.10
  12 Firefox 3.0.6
   9 Firefox 3.0.1
   8 Firefox 3.0.12
   6 Firefox 3.0b5
   6 Firefox 3.0.8
   5 Firefox 3.0b4
   5 Firefox 3.0.7
   2 Firefox 3.1b2
   2 Firefox 3.0.9
   1 Firefox 3.0.4

types of sites that seem to be loaded when the crash happens
 521 
 309 http:
  46 \N
  16 about:blank
  11 https:
   2 file:
   2 about:sessionrestore
   1 chrome:

occurrences and domains of sites where the crash might be happening..
  27 http://www.facebook.com
  23 http://mail.live.com
  16 about:blank//
  13 http://www.youtube.com
  13 http://www.orkut.com.br
   9 http://apps.facebook.com
   6 http://www.tagged.com
   5 http://www.google.com
   5 http://vkontakte.ru
   4 http://messaging.myspace.com
   3 http://www.tuenti.com
   3 http://www.google.co.jp
   3 http://www.friendster.com
   3 http://mail.google.com
and many more...
I asked Lars to get these split out more usefully based on who called |free| (bug 504498 comment 4).

Ted, how can we figure out which extensions might have been involved?  Breakpad is sending that information (bug 366973) but I don't know where I can access it.
Component: Disability Access APIs → Socorro
Product: Core → Webtools
QA Contact: accessibility-apis → socorro
The server-side part of collecting crash extension data is bug 412605.
Depends on: 412605
Whiteboard: cloud
Whiteboard: cloud
Whiteboard: cloud
Whiteboard: cloud → cloud, next
The tools this bug asks for are now in place.  But bug 519356 is going in a different direction.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Crash Signature: [@arena_dalloc_small]
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.