1479251 - TypeError registeredURLs is nul in process-content.js when starting Nightly 63.0a1

Status: VERIFIED FIXED

(DevTools :: Console, defect)

Description

[magicp]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 ID:20180728220145

Steps to reproduce:
1. Start Nightly
2. Open Browser Console (Ctrl+Shift+J)

Actual Results:
The following error is logged in the Browser Console on Windows 10 and Ubuntu 17.10.

TypeError: registeredURLs is null process-content.js:55:13 

Expected Results:
No errors.

Comment 1

[Rares Doghi, Desktop QA]

Hi, I think the Component for this issue is DevTools - Console, please feel free to change it if its not the correct component.

Comment 2

[Nicolas Chevobbe [:nchevobbe]]

Hello, 

I don't think it belongs to the console since it's reporting an error happening in this file.
It looks like Felipe did some work in this file not long ago for Bug 1369466.
Felipe, do you mind having a look at why registeredURLs is null ?

Comment 3

[:Felipe Gomes (needinfo for replies!)]

Do you have a custom homepage?  (i.e., not Firefox Home)

Comment 4

[:Felipe Gomes (needinfo for replies!)]

I tried setting up a custom homepage and couldn't reproduce this issue, so maybe it's caused by some add-on or some other setting that makes process-content to start earlier than the first registration to the RemotePageManager.

In any case, it's simple to fix

Comment 5

[:Felipe Gomes (needinfo for replies!)]

Attachment: Bug 1479251 - registeredURLs may not have been set up yet when the first process launches.

Review commit: https://reviewboard.mozilla.org/r/260452/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/260452/

Comment 6

[Dave Townsend [:mossop]]

Comment on attachment 8996300 [details]
Bug 1479251 - registeredURLs may not have been set up yet when the first process launches.

https://reviewboard.mozilla.org/r/260452/#review267580

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/929ceb6c82fa
registeredURLs may not have been set up yet when the first process launches. r=mossop

Comment 8

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/929ceb6c82fa

Comment 9

[Rares Doghi, Desktop QA]

Hi, I can no longer reproduce this issue in Nightly 63.0a1 (2018-07-31), I will mark it accordingly.

Comment 10

[magicp]

(In reply to :Felipe Gomes (needinfo me!) from comment #3)
> Do you have a custom homepage?  (i.e., not Firefox Home)

I don't have a custom homepage. It is about:home.