NS_ERROR_NOT_INITIALIZED status in nsIHttpChannel · 2010-03-19 09:17 by Wladimir Palant

Dear Lazyweb! Do you have any idea why XMLHttpRequest might fail with channel.status being NS_ERROR_NOT_INITIALIZED? This seems to be happening consistently for some Adblock Plus users when downloading https://easylist-downloads.adblockplus.org/easylist.txt. This issue is happening on all platforms and across all supported Firefox versions (I see 3.0, 3.5, 3.6 in the logs). I tried looking into where NS_ERROR_NOT_INITIALIZED might come from — it isn’t the cache because nsIHttpChannel would swallow the error. It isn’t “304 Not Modified” handling, the error there would be swallowed as well. It isn’t “206 Partial Content” handling — that one only returns NS_ERROR_NOT_INITIALIZED if cache entry is missing, yet without a cache entry a byte range request wouldn’t be made in the first place. It isn’t host resolver because it only returns NS_ERROR_NOT_INITIALIZED on shutdown — having this happen to five consecutive download attempts is very unlikely. Also, Adblock Plus successfully requested the fallback URL immediately after this download failure which is how I learned about that issue so this definitely wasn’t during shutdown. What else can it be?



Commenting is closed for this article.