Closed
Bug 1479251
Opened 6 years ago
Closed 6 years ago
TypeError registeredURLs is nul in process-content.js when starting Nightly 63.0a1
Categories
(DevTools :: Console, defect)
DevTools
Console
Tracking
(firefox-esr52 unaffected, firefox-esr60 unaffected, firefox61 unaffected, firefox62 unaffected, firefox63 verified)
VERIFIED
FIXED
Firefox 63
| Tracking | Status | |
|---|---|---|
| firefox-esr52 | --- | unaffected |
| firefox-esr60 | --- | unaffected |
| firefox61 | --- | unaffected |
| firefox62 | --- | unaffected |
| firefox63 | --- | verified |
People
(Reporter: magicp.jp, Assigned: Felipe)
References
Details
(Keywords: regression)
Attachments
(1 file)
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.
status-firefox61:
--- → unaffected
status-firefox62:
--- → unaffected
status-firefox-esr52:
--- → unaffected
status-firefox-esr60:
--- → unaffected
|
||
Comment 1•6 years ago
|
||
Hi, I think the Component for this issue is DevTools - Console, please feel free to change it if its not the correct component.
Component: General → Console
Product: Toolkit → DevTools
|
||
Comment 2•6 years ago
|
||
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 ?
Flags: needinfo?(felipc)
|
Assignee | |
Comment 3•6 years ago
|
||
Do you have a custom homepage? (i.e., not Firefox Home)
Assignee: nobody → felipc
Blocks: 1369466
Status: NEW → ASSIGNED
Flags: needinfo?(felipc) → needinfo?(magicp.jp)
|
|
Assignee | |
Comment 4•6 years ago
|
||
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
|
||
Updated•6 years ago
|
Keywords: regression
| Comment hidden (mozreview-request) |
|
||
Comment 6•6 years ago
|
||
| mozreview-review | ||
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
Attachment #8996300 -
Flags: review?(dtownsend) → review+
Pushed by felipc@gmail.com:
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•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
|
|
||
Comment 9•6 years ago
|
||
Hi, I can no longer reproduce this issue in Nightly 63.0a1 (2018-07-31), I will mark it accordingly.
Status: RESOLVED → VERIFIED
|
Reporter | |
Comment 10•6 years ago
|
||
(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.
Flags: needinfo?(magicp.jp)
You need to log in
before you can comment on or make changes to this bug.
Description
•