Closed Bug 1372222 Opened 7 years ago Closed 7 years ago

Nightly refuses to load any pages, with console exceptions

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1371714

People

(Reporter: benjamin, Unassigned)

Details

After the weekend I restarted Firefox for an update and now it won't load any pages.

Symptoms:
* On initial restart the browser tried to do a session restore with three windows and some tabs (but not enough)
* each of the tabs was blank, and some didn't have any titles at all

In the error console I see these errors:
NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIScriptSecurityManager.getLoadContextCodebasePrincipal]  remote-browser.xml:370
	remote-browser_XBL_Constructor chrome://global/content/bindings/remote-browser.xml:370:36
	updateBrowserRemoteness chrome://browser/content/tabbrowser.xml:1838:13
	onDOMContentLoaded chrome://browser/content/browser.js:1249:5
	<anonymous> chrome://browser/content/browser.js:1186:5
TypeError: frameLoader.tabParent is null[Learn More]  remote-browser.xml:243:13
	set_docShellIsActive chrome://global/content/bindings/remote-browser.xml:243:13
	updateBrowserRemoteness chrome://browser/content/tabbrowser.xml:1851:41
	onDOMContentLoaded chrome://browser/content/browser.js:1249:5
	<anonymous> chrome://browser/content/browser.js:1186:5

I can open a new tab using the plus button but I can't switch to it with a bunch of JS errors "browser.frameLoader.tabParent is null" and "frameLoader.tabParent is null" 

I can open the browser menu but I cannot open options.

This problem persists even when I quit and relaunch Firefox, although it's remembering fewer windows/tabs each time. After several relaunches I'm down to one window and tab, but still it won't load anything in it.

I was going to try switching session restore off, but I can't open about:config or Firefox preferences.
This was the 2017-06-11 nightly. Applying the next update now.
This appears to have gone away after another update. Is it worth keeping this open?
This sounds like something milan hit late last week in Toronto, where his content process was being killed very soon after start-up. See bug 1371714. Also bug 1368600.
(In reply to Benjamin Smedberg [:bsmedberg] from comment #0)
> NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff
> (NS_ERROR_UNEXPECTED)
> [nsIScriptSecurityManager.getLoadContextCodebasePrincipal] 
> remote-browser.xml:370
> 	remote-browser_XBL_Constructor
> chrome://global/content/bindings/remote-browser.xml:370:36
> 	updateBrowserRemoteness chrome://browser/content/tabbrowser.xml:1838:13
> 	onDOMContentLoaded chrome://browser/content/browser.js:1249:5
> 	<anonymous> chrome://browser/content/browser.js:1186:5
> TypeError: frameLoader.tabParent is null[Learn More] 
> remote-browser.xml:243:13
> 	set_docShellIsActive
> chrome://global/content/bindings/remote-browser.xml:243:13
> 	updateBrowserRemoteness chrome://browser/content/tabbrowser.xml:1851:41
> 	onDOMContentLoaded chrome://browser/content/browser.js:1249:5
> 	<anonymous> chrome://browser/content/browser.js:1186:5

onDOMContentLoaded is brand-new from bug 1371218, so that's slightly concerning at first sight. I only moved the code, so no behavior change is expected. For now I'll assume this isn't the culprit.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.