Closed Bug 1480197 Opened 7 years ago Closed 6 years ago

Crash in the content process due to an assertion in AntiTrackingCommon.cpp

Categories

(Firefox :: Protections UI, defect, P1)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1480780

People

(Reporter: francois, Assigned: baku)

References

Details

I noticed that if I change the third-party domain we use in the antitracking tests: --- a/toolkit/components/antitracking/test/browser/head.js +++ b/toolkit/components/antitracking/test/browser/head.js @@ -1,10 +1,10 @@ const TEST_DOMAIN = "http://example.net/"; -const TEST_3RD_PARTY_DOMAIN = "https://tracking.example.com/"; +const TEST_3RD_PARTY_DOMAIN = "https://tracking.example.org/"; const TEST_PATH = "browser/toolkit/components/antitracking/test/browser/"; const TEST_TOP_PAGE = TEST_DOMAIN + TEST_PATH + "page.html"; const TEST_POPUP_PAGE = TEST_DOMAIN + TEST_PATH + "popup.html"; const TEST_3RD_PARTY_PAGE = TEST_3RD_PARTY_DOMAIN + TEST_PATH + "3rdParty.html"; const TEST_3RD_PARTY_PAGE_WO = TEST_3RD_PARTY_DOMAIN + TEST_PATH + "3rdPartyWO.html"; const TEST_3RD_PARTY_PAGE_UI = TEST_3RD_PARTY_DOMAIN + TEST_PATH + "3rdPartyUI.html"; the content process will hit the following assertion: https://searchfox.org/mozilla-central/rev/196560b95f191b48ff7cba7c2ba9237bba6b5b6a/toolkit/components/antitracking/AntiTrackingCommon.cpp#34 after doing a simple `window.open()`. This feels like there's a problem in the logic there. We shouldn't be crashing the content process. Steps to reproduce: 1. apply the patch above 2. run `./mach test toolkit/components/antitracking/test/browser/browser_blockingCookies.js`
This bug is going to be fixed by bug 1480365.
Is this fixed now?
Flags: needinfo?(amarchesini)
It was fixed by the cookieBehavior pref patches last time I checked. I'll retest it and in case I'll mark it as fixed/dup.
Fixed by bug 1480780.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.