694676 - NS_ERROR_NOT_AVAILABLE in nsIHttpChannel.responseStatus

Status: RESOLVED DUPLICATE of bug 704539

(Firefox :: Sync, defect)

Description

[Olli Pettay [:smaug][[e-mail]]]

On a 64bit Win7 machine the following error happens very often with FF7
1318630300987	Sync.Resource	WARN	Caught unexpected exception Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] Stack trace: _onComplete()@resource://services-sync/resource.js:327 < innerBind()@resource://services-sync/util.js:1159 < Channel_onStopRequest()@resource://services-sync/resource.js:553 in _onComplete.

That seems to lead to showing the error UI, which is annoying.

Comment 1

[Richard Newman [:rnewman]]

It won't show the UI error in future releases of Firefox. Thanks for the report!

Comment 2

[Philipp von Weitershausen [:philikon]]

(In reply to Richard Newman [:rnewman] from comment #1)
> It won't show the UI error in future releases of Firefox.

As much I want this to be true, we don't have a fix for NS_ERROR_NOT_AVAILABLE yet. It bubbles up as Unknown Error every single time.

Comment 3

[Loic]

Attachment: Sync error log about 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus]

Comment 4

[Loic]

Another Sync error log. I joined the log.
Available here too: http://mozservices.pastebin.mozilla.org/1360410

Comment 5

[Harsh86]

I get these errors pretty consistently every hour or so. Any way i can get a more verbose log out of Firefox that will help you guys pinpoint where the problem is?

Comment 6

[Gregory Szorc [:gps]]

This is possibly fixed in bug 690170 (Firefox 10). If not, it is almost certainly fixed in bug 704539 (Firefox 12).

If you still experience the issue after upgrading, please reopen this bug.