Closed Bug 822085 Opened 12 years ago Closed 4 years ago

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

Categories

(Core :: DOM: Navigation, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jruderman, Unassigned, NeedInfo)

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

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.
Attached file testcase
Attached file 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.

Hi Jesse!
With the attached test case, I was not able to reproduce this issue on Firefox Release version 85.0, and ESR version 78.7.0 on Windows 10.
Because firefox has changed quite a bit, we would like to close it.
Could you tell us if the same problem still happens?

Flags: needinfo?(jruderman)

Hi,
I'm marking this as Resolved-Incomplete due to lack of response. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.
Thanks,

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: