Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heavy usage of a certain userscript results in NS_ERROR messages #1764

Closed
hurda opened this issue Jul 13, 2013 · 3 comments
Closed

Heavy usage of a certain userscript results in NS_ERROR messages #1764

hurda opened this issue Jul 13, 2013 · 3 comments

Comments

@hurda
Copy link

hurda commented Jul 13, 2013

I have no reliable way to reproduce these error-messages, so I'm just basing this report on my observations.

The userscript in question is YouTube Link Title. It changes plain YouTube-links to display the video's title.

Whenever I see that there were many links, which had been modified by this script, on message boards, the following error would be shown in the console:

Sat Jul 13 2013 23:38:08
Error: NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIDOMJSWindow.setTimeout]
Source file: file:///C:/Users/user/AppData/Roaming/Mozilla/Firefox/Profiles/wrtk00m5.sm/gm_scripts/YouTube_Link_Title/83584.user.js
Line: 85

Most of the time, shortly after these errors begin to appear, the following error would popup when ever I middle-click on a page for autoscrolling:

Error: 'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent] = NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED
Source file: chrome://global/content/bindings/popup.xml
Line: 112

I'm only reporting this now because of popups being mentioned in #1762, and maybe those two problems have some correlation.

EDIT:
Another reason for this report is that this userscript is generating a submenu in the GM-menu, hence the reference to #1762.

@hurda
Copy link
Author

hurda commented Jul 17, 2013

After more testing, I was able to replicate the handleEvent-error in 22 and 23 without any addons installed, but not in 24 or 25. No idea if the bug is actually fixed, or if the new error console is just not showing it.

So I guess this issue can be closed, as it's a bug of the browser.

Anyway, should I file a new issue for the nsIDOMJSWindow.setTimeout-error, or is that just an error in the userscript, for stuff like waiting to long for a server-reply or something?

@arantius
Copy link
Collaborator

The best thing to do is to try to write a reduced test case, without Greasemonkey involved. Like I did here:
https://bugzilla.mozilla.org/show_bug.cgi?id=846316
Using Scratchpad and chrome privileges is easy and easily reproducible.

If you can do so, close this bug and report one upstream with Firefox, because it's a bug on their side and not ours. If you can do so in release versions but not nightlies, then it's probably already fixed so just close this.

@hurda
Copy link
Author

hurda commented Jul 17, 2013

Ok, thank you for the advice.

@hurda hurda closed this as completed Jul 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants