Need help with NS_ERROR_NOT_INITIALIZED

Talk about add-ons and extension development.
Post Reply
adam-p
Posts: 2
Joined: January 24th, 2014, 7:56 pm

Need help with NS_ERROR_NOT_INITIALIZED

Post by adam-p »

A few of my users (and I) have encountered a super annoying bug with my extension where it will stop working until the browser is restarted or another browser window is used. Here's the error in the browser console:

Code: Select all

[13:29:46.827] Markdown Here: failing back to content script preferences code
[13:29:46.827] [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIDOMJSWindow.setTimeout]"  nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)"  location: "JS frame :: resource://markdown_here_common/utils.js :: nextTick :: line 469"  data: no]
[13:29:46.827] ReferenceError: document is not defined @ resource://markdown_here_common/options-store.js:339


It seems to happen sporadically. (Once a day? Every few hours?) It has mostly been reported for Windows, but also Ubuntu.

Here are links to the reports of the issue, but there's not much useful information there.
https://github.com/adam-p/markdown-here/issues/141
https://github.com/adam-p/markdown-here/issues/153
https://groups.google.com/forum/#!topic ... kXFqkP77Ws

I have done a bunch of googling for this, and there are plenty of instances of similar errors, but I haven't found any solutions.

I'm at loss for ideas on what else to try, so I'd appreciate any help or suggestions.

Adam
User avatar
LoudNoise
New Member
Posts: 39900
Joined: October 18th, 2007, 1:45 pm
Location: Next door to the west

Re: Need help with NS_ERROR_NOT_INITIALIZED

Post by LoudNoise »

Are you using your extension is an otherwise clean profile?
Post wrangler
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
adam-p
Posts: 2
Joined: January 24th, 2014, 7:56 pm

Re: Need help with NS_ERROR_NOT_INITIALIZED

Post by adam-p »

LoudNoise wrote:Are you using your extension is an otherwise clean profile?


No, and I'm sure my users aren't.

Are you suggesting that another extension behaving badly could cause that error in mine?
User avatar
LoudNoise
New Member
Posts: 39900
Joined: October 18th, 2007, 1:45 pm
Location: Next door to the west

Re: Need help with NS_ERROR_NOT_INITIALIZED

Post by LoudNoise »

Assuming this is still true [quote] Interesting. That code is only supposed to be hit (iirc) when the rendering is being done from the options page — not under normal email circumstances.[;/quote]

that is where I would start. If it doesn't happen in a clean profile it means that it is likely your extension isn't the problem by itself. Then it just a matter of comparing set ups and figuring out what caused it. If it does happen then it is a matter figuring out which change to FX caused the problem.

Altough you don't maintain a support thread here, if this was a wide spread problem that has been around for long we would have heard about.
Post wrangler
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
jmozmoz
Posts: 365
Joined: August 3rd, 2009, 12:28 pm

Re: Need help with NS_ERROR_NOT_INITIALIZED

Post by jmozmoz »

Ok. This thread is very old, but I also see this problem with an extension for Thunderbird. It is cause by this line:
https://github.com/jmozmoz/compactheade ... 9C%93#L744

Here are the logs of mozmill tests, which trigger this bug:
https://travis-ci.org/jmozmoz/compacthe ... /340264744

It seems only to happen, if there are to many calls to the setTimeout function.

Any idea how to fix this?
Post Reply