Closed Bug 1322846 Opened 9 years ago Closed 9 years ago

this listener is not a function

Categories

(Firefox :: Untriaged, defect)

53 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: grgoffe, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20161210030206 Steps to reproduce: During FF Nightly operations, the following messages appear frequently: console.error: Message: TypeError: this.listener is not a function Stack: observe@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/events.js:81:7 Actual results: see above Expected results: code should be corrected to stop the appearance of this message.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Errors appear during startup or restart of FF Nightly.
Hello George, I believe those console errors are generated in connection with an add-on. Could you perhaps start Nightly with a new clean profile and reply if the errors are still visible when running Nightly with the new profile? in case there is needed see profile management: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_starting-the-profile-manager
Flags: needinfo?(grgoffe)
Resolving as incomplete. George, please reopen this if you come with the above requested info.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Adrian, Thanks for your efforts with this. I'm not very sure just where the message comes from. A library? From static constants within an add-on? Is there a place in ~/.mozilla/firefox/<profile-id> where add-ons are stored? I'm thinking just a series of "strings <plugin> | grep 'listener'" commands might give us a clue as to which plugin the message comes from. I have 15 or so plug-ins installed and seem to get the message at random times but with a rather large number of tabs "active" (i.e., > 300). This makes removing a plugin... starting LOTS of tabs and praying for the message to NOT appear... which is not deterministic since the message may be random. Sigh... Again, thanks for your efforts, George...
Flags: needinfo?(grgoffe)
You need to log in before you can comment on or make changes to this bug.