"Assertion failure: failedURI (We don't have a URI for history APIs.)" with onunload navigation to error page

NEW
Unassigned

Status

()

Core
Document Navigation
--
critical
6 years ago
6 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 2 bugs, {assertion, testcase})

Trunk
x86_64
Mac OS X
assertion, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

6 years ago
Assertion failure: failedURI (We don't have a URI for history APIs.), at docshell/base/nsDocShell.cpp:7817

Opposite of bug 750145?

Bug 820200 has the same assertion message, but otherwise seems unrelated.
(Reporter)

Comment 1

6 years ago
Created attachment 692702 [details]
testcase
(Reporter)

Comment 2

6 years ago
Created attachment 692703 [details]
stack
> Opposite of bug 750145?

Bug 750145 was about subframe loading. This bug seems independent.

The main problem here is "unload" handler clears nsDocshell::mFailedURI, which must not be null during trying to display an error page. A little more serious problem is probably URILoader called DoContent() (and CreateContentViewer()) after |window.close()| would have been called.
You need to log in before you can comment on or make changes to this bug.