Crash in [@ mozilla::AntiTrackingCommon::IsStorageAccessPermission]
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: marcia, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-70d882b0-5cf3-459c-a0c3-ab8f40190326.
Fairly small volume regression spotted during nightly crash triage - not sure if I got the component correct or not: https://bit.ly/2WsWShV. 9 crashes/2 installs on 68 and at least crash in 67 nightly. There also appears to be a small number of crashes in 65. ni on :ehsan since he might have some insight
Top 10 frames of crashing thread:
0 xul.dll mozilla::AntiTrackingCommon::IsStorageAccessPermission toolkit/components/antitracking/AntiTrackingCommon.cpp:1043
1 @0x20ab205ce7bf
2 xul.dll mozilla::storage::StorageBaseStatementInternal::ExecuteAsync storage/StorageBaseStatementInternal.cpp:185
3 @0x1394217166f
4 xul.dll void nsPermissionManager::NotifyObserversWithPermission extensions/cookie/nsPermissionManager.cpp:2756
5 xul.dll nsPermissionManager::AddInternal extensions/cookie/nsPermissionManager.cpp
6 xul.dll nsPermissionManager::AddFromPrincipal extensions/cookie/nsPermissionManager.cpp:1756
7 xul.dll mozilla::AntiTrackingCommon::StoreUserInteractionFor toolkit/components/antitracking/AntiTrackingCommon.cpp:1822
8 xul.dll mozilla::dom::ContentParent::RecvStoreUserInteractionAsPermission dom/ipc/ContentParent.cpp:5692
9 xul.dll mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:8438
Comment 1•6 years ago
|
||
Andrea, does this make any sense to you? Looks like the principal pointer is somehow corrupted? But we're also in the main process where we shouldn't have an outer window with a content principal. This looks very suspect to me. Maybe we're seeing a memory corruption issue?
Comment 2•6 years ago
|
||
One crash only in Beta, marking as wontfix for 67.
Comment 3•6 years ago
|
||
We haven't seen any new crashes with this signature. It could be something corrupted on that particular installation?
Also the stack trace looks corrupted. I would close this bug as wontfix until we see new crash reports.
Reporter | ||
Comment 4•6 years ago
|
||
Based on Comment 3 I am going to won't fix this bug. If it reappears we can reopen. Also adjusting tracking flag for 68.
Description
•