sendRemoveListener on closed conduit errors spams the console
Categories
(WebExtensions :: General, defect, P3)
Tracking
(firefox77 affected)
Tracking | Status | |
---|---|---|
firefox77 | --- | affected |
People
(Reporter: kernp25, Unassigned)
References
Details
Attachments
(4 files)
I know, that it is expected, that it should throw the error to the console, but it really spams the console with this error: sendRemoveListener on closed conduit simple-translate@sienori.549755894884
I also see one time in console: sendAddListener on closed conduit simple-translate@sienori.549755894554
It seems to happen often with this add-on installed: https://addons.mozilla.org/firefox/addon/simple-translate/
Comment 3•4 years ago
|
||
Hello,
I have managed to reproduce the console error you encountered on the latest Nightly (77.0a1/20200429215539), Beta (76.0/20200429185419) and Release (75.0/20200403170909) under Windows 10 Pro 64-bit and Ubuntu 16.04 LTS, however, not during normal usage of the add-on.
To reproduce the error I’ve employed the following STR:
- Install the extension
- Go to about:debugging and access the add-on console via “Inspect”
- On the “Console” tab, refresh the page by pressing F5
Note: Each press of F5 will produce a new set of the same error (the number after the add-on id changes with each refresh)
Are you doing anything in particular for this add-on to spam the console with the error or just normal usage of the add-on functions?
(In reply to Alex Cornestean from comment #3)
Are you doing anything in particular for this add-on to spam the console with the error or just normal usage of the add-on functions?
This add-on runs in the background and i'm using it sometimes.
Maybe there is a bug in the add-on itself?
For example.
I'm able to reproduce the scenario from Alex with many extensions (µBlock, decentraleyes, NoScript to name a few).
Updated•4 years ago
|
I have successfully reproduced this error.
The following listeners in the background script causes the error.
browser.storage.onChanged.addListener(() => {});
browser.contextMenus.onClicked.addListener(() => {});
I don't know how the developer can resolve this error.
Is this normal, that if you open the extension popup and then closes it, it does throw the error (every time)?
Can you confirm, that open and closing the extension popup (uBlock Origin) will throw the error?
Comment 10•4 years ago
|
||
Hello,
I can confirm the behavior stated in Comment 9 by kernp25.
Tested with uBlock Origin on the latest Nightly (78.0a1/20200504205324), Beta (77.0b1/20200504222419) and Release (75.0/20200403170909) under Windows 10 Pro 64-bit and Ubuntu 16.04 LTS.
Closing and opening the extension’s popup will throw the mentioned error.
Updated•4 years ago
|
Comment 11•4 years ago
|
||
The error message is not actionable, so we should remove it from the console.
I'm bumping the priority because it is not only logspam, it can also interfere with actual internals. As seen in bug 1640866, this bug can interrupt the cleanup of internals. Bad things could happen...
Comment 12•4 years ago
|
||
Any progress on this?
Comment 13•4 years ago
|
||
This is an unassigned bug, so safe to say that there is no progress.
Comment 14•3 years ago
|
||
(In reply to kernp25 from comment #7)
Created attachment 9145190 [details]
ER13Go7H4p.mp4Tested with uBlock Origin.
hi.
Did you find the reason of such behavior?
Comment 15•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 11 votes.
:mixedpuppy, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 16•2 years ago
|
||
When testing my extension with Event Pages ("persistent": false
), this error is logged each time the page is idle.
It is very annoying.
Description
•