1431580 - NS_ERROR_NOT_INITIALIZED: browser.js:4770

Status: RESOLVED INVALID

(DevTools :: General, defect)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180113113216

Steps to reproduce:

From start with clean profile


Actual results:

I got this form console: NS_ERROR_NOT_INITIALIZED:  browser.js:4770


Expected results:

No errors.

Thanks!

Comment 1

[Abe - QA (:Abe_LV)]

Hi Wellington,

I have tried this on Ubuntu 16.04 amd64 with latest nightly but could not see "NS_ERROR_NOT_INITIALIZED" on the console.

Are there specific steps I should follow?  

I tried these:
First try - Open Firefox from a clean profile and check the log in the browser console.
Second try - Start Firefox using "./firefox --jsconsole --jsdebugger --wait-for-jsdebugger --devtools --no-remote" and check for errors in the console

Comment 2

[Wellington Torrejais da Silva]

Hi,

This error is JS classified like this bellow(I got this error too):

01:32:29.359 Error: Could not establish connection. Receiving end does not exist. 1 undefined

Please try to show all filter categories.

Thanks

Comment 3

[Patrick Brosset <:pbro>]

There seems to be 2 errors being discussed here, nothing seems to show that they're related, so 2 separate bug reports might be better.

1. NS_ERROR_NOT_INITIALIZED:  browser.js:4770
2. Error: Could not establish connection. Receiving end does not exist.

Error 1 is coming from browser.js, there is a file named like this in DevTools, but it doesn't have 4770 lines, so I suspect this is coming from the browser UI's browser.js file instead.
Without more information, this will be hard to investigate. I can't reproduce this myself. I opened Firefox with a new profile, and then opened the console (without any filters), but couldn't see this error.

As for error 2: I know that it is usually from addons using WebExtensions APIs to send messages across processes. This seems weird if you said you started from a clean profile, without addons.
But also, it's going to be really hard to find out what the problem is without more information here again. If the console contains a stack trace, that would be very helpful.
Also here, I can't reproduce the issue.

Keeping the bug as unconfirmed for now.

Comment 4

[Wellington Torrejais da Silva]

Thank Patrick for the information.

I will try to find and describe the bugs more detailed.

Comment 5

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Not enough information to proceed and no activity in 2 years, closing.

Feel free to reopen if you can reproduce this and provide more details about STR.

Honza