1737371 - Crash in [@ mozilla::dom::SessionHistoryEntry::RemoveLoadId]

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect, P5)

Description

[Sean Feng [:sefeng]]

Crash report: https://crash-stats.mozilla.org/report/index/6bb6f23d-351b-49b9-a5ec-56e450211021

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0 XUL mozilla::dom::SessionHistoryEntry::RemoveLoadId docshell/shistory/SessionHistoryEntry.cpp:399
1 XUL mozilla::dom::SessionHistoryInfo::FillLoadInfo const docshell/shistory/SessionHistoryEntry.cpp:243
2 XUL nsSHistory::RemoveEntries docshell/shistory/nsSHistory.cpp:1899
3 XUL mozilla::AppWindow::SavePersistentAttributes xpfe/appshell/AppWindow.cpp:2055
4 XUL mozilla::AppWindow::SavePersistentAttributes xpfe/appshell/AppWindow.cpp:2104
5 XUL nsDocLoader::cycleCollection::TraverseNative uriloader/base/nsDocLoader.cpp:209
6 XUL nsDocLoader::Destroy uriloader/base/nsDocLoader.cpp:386
7 XUL nsresult NS_ReadLine<char, nsIInputStream, nsTString<char> > netwerk/base/nsReadLine.h:84
8 XUL XUL@0x92044a 
9 XUL nsresult NS_ReadLine<char, nsIInputStream, nsTString<char> > netwerk/base/nsReadLine.h:126

This seems to be a null pointer crash, however, I don't see why.

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

The stack trace looks rather bogus.

Comment 2

[Chris Peterson [:cpeterson]]

Three crash reports from three different users on the same 95.0a1 build id on the same day. I know they are three different users because the three crash reports have different extensions installed.

Comment 3

[Hsin-Yi Tsai (she/her) [:hsinyi]]

The crashes seem to disappear. Close?

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.