348473 - crash [@ 0x134863b1 fffb12bf ] [@ PL_DestroyEvent() ] opening link in new tab

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Tony Mechelynck [:tonymec]]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060812 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060812 Firefox/1.5.0.6 - Build ID: 2006081204

TB22030188G


Reproducible: Didn't try

Actual Results:  
crash

Expected Results:  
no crash

Incident ID: 22030188
Stack Signature	0x134863b1 fffb12bf
Product ID	Firefox15
Build ID	2006081204
Trigger Time	2006-08-12 14:50:33.0
Platform	LinuxIntel
Operating System	Linux 2.6.11.4-21.13-default
Module	
URL visited	alas, Fx has crashed, the address is gone now
User Comments	opening a link in a new tab
Since Last Crash	2 sec
Total Uptime	2 sec
Trigger Reason	SIGSEGV: Segmentation Fault: (signal 11)
Source File, Line No.	N/A
Stack Trace 	
0x134863b1
PL_DestroyEvent()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/xpcom/threads/plevent.c, line 728]
PL_HandleEvent()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/xpcom/threads/plevent.c, line 699]
PL_ProcessPendingEvents()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/xpcom/threads/plevent.c, line 623]
nsEventQueueImpl::ProcessPendingEvents()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/xpcom/threads/nsEventQueue.cpp, line 421]
event_processor_callback()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/widget/src/gtk2/nsAppShell.cpp, line 67]
libglib-2.0.so.0 + 0x4a69f (0x405fd69f)
libglib-2.0.so.0 + 0x23967 (0x405d6967)
libglib-2.0.so.0 + 0x25ce2 (0x405d8ce2)
libglib-2.0.so.0 + 0x26cf7 (0x405d9cf7)
libgtk-x11-2.0.so.0 + 0x116be3 (0x402d6be3)
nsAppShell::Run()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/widget/src/gtk2/nsAppShell.cpp, line 141]
nsAppStartup::Run()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 151]
XRE_main()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/toolkit/xre/nsAppRunner.cpp, line 2376]
main()  [/builds/tinderbox/Fx-Mozilla1.8.0/Linux_2.4.21-37.EL_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 62]
libc.so.6 + 0x14e80 (0x40a1ee80)

Comment 1

[Adam Guthrie]

Tony, I have a feeling that one of your extensions is abusing something. Are you using as many extensions that you listed in attachment 233306 [details]? If you're willing, could you disable all your extensions for a week, and see if you're still as crash happy?

Comment 2

[Tony Mechelynck [:tonymec]]

(In reply to comment #1)
> Tony, I have a feeling that one of your extensions is abusing something. Are
> you using as many extensions that you listed in attachment 233306 [details] [edit]? If you're
> willing, could you disable all your extensions for a week, and see if you're
> still as crash happy?
> 

/All/ of them? For a /week?/ Sorry, but if that is the only thing to do I'd rather return to Opera or Konqueror. Some of those extensions I couldn't live (well, browse) without: Tab Mix Plus allows my tabs to flow on additional tab bars and reloads them after a suhtdown or a crash. MR-Tech Local Install (which I use on both Firefox and Thunderbird) has, among other things, several useful features to manage add-ons (it produced the neat HTML listing in the attachment), and a "Paste User Agent and Build ID" feature which I've found useful on Bugzilla: see e.g. the "Build Identifier" paragraph here at top; it is even more useful for Thunderbird, where the UA srtring isn't readily accessible without an extension. Those with names starting deviant- I constantly use on the site I visit most often.

OK, now there /are/ some extensions which I could disable without shedding a tear, but most of them I hardly ever use, so I doubt that they would be at the source of the crash. Let's review the list in the attachment:
- abcTajpu : it's neat but I can paste from UTF-8 Vim if I have to.
- BBCodeXtra : if needed, I can type the BB codes manually.
- Calculator : I hardly ever use it.
- ColorZilla : ditto.
- DOM Inspector : ditto (but maybe you'll say I can keep it).
- Editus Externus : I hardly ever use it.
- FireFTP : not only do I hardly ever use it, it doesn't work properly.
- Flags : I can live without it, but I'd rather like to keep it.
- keyconfig : I don't use it much, but I may someday have to, since kde preempts many Ctrl-something key combinations.
- Print Preview : I don't need it, until I get a printer again.
- Target Alert : I can live without it, but I'd rather like to keep it.
- Tinderstatus : that one isn't really useful to me, since I haven't found how to  make it monitor the Mozilla1.8.0 tree (Fx/Tb 1.5.0.x) rather than the Seamonkey trunk. Its "refresh" function might -or might not- have something to do with timeouts and race situations.

The "Silver Skin" theme is installed but not in service -- alas, that one produces /solid/ crashes. If it gets updated I may try it again -- or not.

The other extensions (those not listed above) I'd rather keep, even at the cost of experiencing a crash every day or two. OK, that's much too often for a supposedly "released" version, but I'm getting the hang of using Talkback; the talkback-public report form is bookmarked, and the clipboard wasn't invented for nothing ;-). If my crash reports can help solve errors in Firefox, so much the better; if they can't, well, at least I shall have tried, and thanks to Tab Mix Plus my session will get reloaded.

I have noticed that several of my "crashing" bugs are marked as "fixed in 2.0" so I tried unziptarring that one tonight; but I had to go back because my most useful extensions were declared "incompatible", and even though compatibility-disable is off by default, my session didn't reload.

So my point of view is: I will disable the extensions listed earlier in this comment, or some of them, if you ask me to; I "need" the others even if it means I'll get crashes every couple of days; turning all extensions off would make Firefox less attractive to me than Opera or Konqueror.

Comment 3

[Tony Mechelynck [:tonymec]]

Attachment: list of extensions as of 2nd crash

very similar crash TB22069625W with some extensions disabled (see list attached)

Comment 4

[Tony Mechelynck [:tonymec]]

Attachment: 2nd crash stack trace

AFAICT, the only difference between this crash trace and the original trace is the top (most recent) address in the stack, which (unlike most others) has no symbolic label

Comment 5

[Adam Guthrie]

Would you mind disabling Forecastfox, too? I have a feeling this is the culprit.

Comment 6

[Tony Mechelynck [:tonymec]]

(In reply to comment #5)
> Would you mind disabling Forecastfox, too? I have a feeling this is the
> culprit.
> 

Well... I'll do it; but is it a mere hunch, or has there been more incidents where ForecastFox was present?

Comment 7

[Tony Mechelynck [:tonymec]]

Attachment: extensions (3rd crash)

similar crash TB22137122H but "Illegal instruction" this time.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7pre) Gecko/20060815 Firefox/1.5.0.7pre - Build ID: 2006081504

Forecastfox is disabled.

Clicking the titlebar to make the menu disappear. The menu in question is "(RightClick) -> deviantLink to <name> -> Gallery -> All categories", added by deviantLink, an extension which I'm not going to disable. Its 3rd-level context menu has a tendency not to disappear after mddle-clicking a menu item to open it in a new tab.

Comment 8

[Tony Mechelynck [:tonymec]]

Attachment: stack trace (3rd crash)

Comment 9

[Tony Mechelynck [:tonymec]]

"A new version of DeviantLink is available". Don't know if it's the culprit but I guess it shouldn't be bad to upgrade (2.0.4 -> 2.10). Then I re-enable ForecastFox (which apparently wasn't the culprit) and restart Firefox.

Comment 10

[Tony Mechelynck [:tonymec]]

crash TB22662515E clicking on a menu in the deviantLink extension's custom toolbar. I smell a rat (cf. comment #7 ).

Comment 11

[Tony Mechelynck [:tonymec]]

TB22674833K -- canceling a menu after opening it but not triggering it (I had changed my mind).

Comment 12

[Wayne Mery (:wsmwk)]

Tony, still see this?

Comment 13

[Tony Mechelynck [:tonymec]]

(In reply to comment #12)
> Tony, still see this?

Hm, if I had seen it in Fx2 I suppose I would have listed a Talkback dump for it, or at least have opened a dupe if I forgot about this one; but OTOH I switched away from Fx2 only quite recently, after using its very last hourly for maybe a week or two. The fact that apparently I didn't ever see this bug all the time I was using Fx2 seems to indicate it's been fixed somewhere.

=> WFM.