452053 - random crashes on right click

Status: VERIFIED WORKSFORME

(Firefox :: General, defect)

Description

[J S]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); pl-PL; Alexa Toolbar; rv:1.9.0.1) Gecko/2008070400 SUSE/3.0.1-2.1 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); pl-PL; Alexa Toolbar; rv:1.9.0.1) Gecko/2008070400 SUSE/3.0.1-2.1 Firefox/3.0.1

Firefox crashes randomly on rightclick. FF window instantly closes, no error message or anything. It happened couple of times while clicking on a page or address bar.

Reproducible: Sometimes

Steps to Reproduce:
1. Rightclick anywhere.
Actual Results:  
Firefox window closes

Expected Results:  
Right-button menu should be displayed

Comment 1

[Matthias Versen [:Matti]]

Do you get the same in the firefox safemode ?
- http://support.mozilla.com/en-US/kb/safe+mode

Please provide a stack trace with debug symbols

Comment 2

[J S]

I can't reproduce it in safe mode.

Comment 3

[Matthias Versen [:Matti]]

That means that one extension is causing this.
Please disable the addons one by one in tools/addons to find the addon that is causing this. It should be an addon that is adding something to the right-click menu, for example a download-addon.

Comment 4

[J S]

OK, how do I provide a stack trace? I'm using Firefox from openSUSE 10.2 repo and I have debuginfo package installed, but what now? It's really hard to trace faulty addon by disabling them one-by-one. I'm using six addons and crash occurs very rarely (once a day or once in two days), so even if I disable an addon and everything is OK for 2 or 3 days I can't be 100% sure, that I found the faulty addon.

And I noticed, that this random crash happens not only on right click, but also when opening dialog window ("Save page as..." for example).

Comment 5

[timeless]

please see bug 422916 comment 14 

matti, please add that to your list

Comment 6

[J S]

Hm.. I'm trying to get the backtrace using the method described in bug 422916 comment 14 and it doesn't seem to work. All I get is info that it's a segmentation fault, but that's not very informative. When starting FF I also get a lot of "No debugging symbols found" on the console. Does it mean, that debuginfo package for FF doesn't work or is it about some other components used by FF (like gtk)?

Comment 7

[J S]

I updated to FF 3.0.3 and the problem still exists.

Comment 8

[J S]

Attachment: Debuging output from console

Comment 9

[J S]

Attachment: Another stacktrace

Message at the end of file ("Naruszenie ochrony pamieci") means "Memory protection fault".

Comment 10

[J S]

Are these attachments useful in any way? This bug is pretty annoying and I'm considering switching to different browser.

Comment 11

[Matthias Versen [:Matti]]

we need a stacktrace from gdb with debugging symbols. (comment #5)
Mozilla.org builds are coming with a buildin crash reporter and it's much easier with that.
Note: I can not help more with debugging under Linux as win32 user.

Comment 12

[timeless]

comment 8 points to bug 444055 and some other bug which i can't find atm. comment 9's output is absolutely worthless.

Comment 13

[J S]

Ok, so I got Firefox from Mozilla, not from SuSE repository. The problem still occurs. Crash reporting doesn't work - when I want to send a report it says that it's sending a report, but actually nothing happens (I left it for over an hour). I found Crash Reports directory under ~/.mozilla/firefox. In pending directory there are *.dmp and *.extra files which, I assume, should be sent to mozilla by crashreporter. Will it be useful if I provide them? Unfortunately I don't get any "core" files, so I can't provide stacktrace as described in "Bug writing guidelines".

Comment 14

[Matthias Versen [:Matti]]

There should be s submit.log, we can't manually put the .dmb file on the server or better i don't know how to do that.
Do you have a 32 bit curl libary installed (breakpad needs that) ?

Comment 15

[J S]

submit.log is empty (0 bytes). My curl library is 64-bit, but I have curl-32bit compatibility library. 

So providing *.dmp files as an attachment won't help? Any other way of providing a stacktrace (or idea why there is no "core" file after a crash)?

Comment 16

[J S]

I deleted my ~/.mozilla folder and installed add-ons from scratch. I installed Tab Mix Plus (which I had previously installed), Adblock Plus and Download Statusbar (these two are new - I didn't have them earlier). The problem still occurs, which means that either it's caused by Tab Mix Plus or it's not a matter of any add-on. 

Any help on providing a stacktrace?

Comment 17

[Tyler Downer [He/Him]]

Have you tried not installing Tab Mix plus at all, but with a clean unmodified profile?

Comment 18

[J S]

No I haven't since Tab Mix Plus is a must-have for me.

Comment 19

[Tyler Downer [He/Him]]

Create a new profile (http://support.mozilla.com/kb/profile), your old one will be saved, then see if it happens. If the crash does not occur, contact the vendor of Tab Mix Plus.

Comment 20

[Wayne Mery (:wsmwk)]

Reporter,

It's great that you reported the bug, but we need to move the bug toward some  resolution with your help.  Please provide additional information using the previous detailed hints mentioned in the bug.

If on the other hand you no longer see the problem, kindly close the bug by setting status to RESOLVED and change resolution to WORKSFORME.  Thanks.

Comment 21

[J S]

About a week ago I installed latest version of SuSE and the problem is gone. I'm marking the bug as WORKSFORME. Unfortunately I wasn't able to provide a proper backtrace earlier :(