Browser crash when calling method toSource on nsIEventListenerInfo object

NEW
Unassigned

Status

()

--
critical
5 years ago
3 years ago

People

(Reporter: droland, Unassigned)

Tracking

({crash, crashreportid})

23 Branch
x86_64
Linux
crash, crashreportid
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bugday-20131021], crash signature)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130803215302

Steps to reproduce:

I am writing an add on, developing with Firefox Ver 23.0 on Ubuntu Linux. My add-on's javascript accesses the nsIEventListenerService getListenerInfoFor method to obtain a list of nsIEventListenerInfo objects for each dom node on a page. I then call the method toSource on each of this listener info objects.


Actual results:

The browser crashes when I visit the page http://www.surfline.com/home/index.cfm. I was able to isolate the cause of the crash to calling the toSource method of a nsIEventListenerInfo object but cannot figure out which listener info object is causing the crash. This is happening today (Oct 11, 2013).  I can tell you that the offending object has these attributes - allowsUntrusted is false, capturing is false, inSystemEventGroup is false, and type is "click".


Expected results:

The browser should not crash the the toSource method should return a string or null.

Comment 1

5 years ago
Can you please post a crash report ID using the instructions at https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report ?
Flags: needinfo?(droland)
Keywords: crash
(Reporter)

Comment 2

5 years ago
(In reply to Suzanne Smedberg from comment #1)
> Can you please post a crash report ID using the instructions at
> https://developer.mozilla.org/en-US/docs/
> How_to_get_a_stacktrace_for_a_bug_report ?

I can't seem to get the crash report using the instructions. I'm on Ubuntu Linux, and after the crash, the browser does not display the dialoge to submit a crash report. I've also checked the about:crashes page and it's empty (no crashes). In my preferences, I have the submit crash reports option checked. I can say that the browser continues to crash every time that I run through the steps submitted in the bug.
Flags: needinfo?(droland)

Comment 3

5 years ago
If you are using the Ubuntu Firefox, we can't help you - Ubuntu creates its own builds, and our crash reporting service doesn't play well with it.  If you are using Firefox downloaded from Mozilla, then we're in business.

Comment 4

5 years ago
Reporter, please try with a build from Mozilla, like the latest Nightly from https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/, and possibly a release from https://www.mozilla.org/
Severity: normal → critical

Updated

5 years ago
Flags: needinfo?(droland)
Whiteboard: [bugday-20131021]
(Reporter)

Comment 5

5 years ago
(In reply to Aleksej [:Aleksej] from comment #4)
> Reporter, please try with a build from Mozilla, like the latest Nightly from
> https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-
> central/, and possibly a release from https://www.mozilla.org/

The crash report id is 120c8fd4-cdab-469b-ab3d-a6d4c2131023.
https://crash-stats.mozilla.com/report/index/120c8fd4-cdab-469b-ab3d-a6d4c2131023

Please let me know if you need more information.david
Flags: needinfo?(droland)

Comment 6

5 years ago
Thanks, david.
Let's suppose it's in Core::DOM, like bug 877515.
Status: UNCONFIRMED → NEW
Crash Signature: [@ mozilla::dom::CallbackObject::Callback() const ]
Component: Untriaged → DOM
Ever confirmed: true
Keywords: crashreportid
Product: Firefox → Core

Updated

3 years ago
Crash Signature: [@ mozilla::dom::CallbackObject::Callback() const ] → [@ mozilla::dom::CallbackObject::Callback() const ] [@ mozilla::dom::CallbackObject::Callback const ]
You need to log in before you can comment on or make changes to this bug.