In Firefox (firefox-120.0-2.fc39), when "Enhanced Tracking Protection" is set to "strict", Google Maps becomes unusable. Here the profile for that case: https://share.firefox.dev/3GhYrYE Reproducible: Always Steps to Reproduce: 1. Use Fedora's build of Firefox 120 2. In Settings, go to "Privacy and Security" and there set "Enhanced Tracking Protection" to "strict" 3. Open Google Maps and try move the map around Actual Results: The result for me is that the tab in Firefox hangs and I need to close it. Expected Results: The tab should stay responsive. Tested the following versions each with a clean profile: Fedora's Firefox 119 : OK Fedora's Firefox 120 : FAIL Mozilla's Firefox 120 : OK Mozilla's Firefox 121b2 : OK Mozilla's Firefox 122a1 : OK Mozilla's builds work for me, only Fedora's build of Firefox seems affected.
Hm, I wonder why Fedora builds fails. Can you try to capture profile with Mozilla's Firefox 120 and attach it here? Also please attach about:support page from Fedora. Do you test on the same profile? Can you test Fedora Firefox with new / clean profile without extensions? Thanks.
Created attachment 2001076 [details] Fedora's Firefox 120 about:support (clean profile)
Here the profile with a Mozilla's build that works: https://share.firefox.dev/3sVWvlD (I also set the "Enhanced Tracking Protection" to strict there) For every test I created a completely new profile without installing any extensions.
FWIW, I get google maps to freeze with both "strict" and "standard". However, if I select "custom" and leave everything except "suspected fingerprinters", google maps works.
Edit: if I leave everything _enabled_, except for "suspected fingerprinters". So anti-fingerprinting seems to trigger the freeze for me.
Thanks. Looks like mozilla::nsRFPService::RandomizePixels() takes much more time in Fedora Firefox than Mozilla Firefox.
Confirmed as gcc issue, moved upstream - https://bugzilla.mozilla.org/show_bug.cgi?id=1866409
*** Bug 2251620 has been marked as a duplicate of this bug. ***
FEDORA-2023-900ec9c782 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-900ec9c782
FEDORA-2023-900ec9c782 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-1e3687a761 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1e3687a761
FEDORA-2023-dce9c4b01f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dce9c4b01f
FEDORA-2023-60a3e530b7 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-60a3e530b7
FEDORA-2023-1e3687a761 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1e3687a761` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1e3687a761 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-60a3e530b7 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-60a3e530b7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-60a3e530b7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-dce9c4b01f has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-dce9c4b01f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dce9c4b01f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-60a3e530b7 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-1e3687a761 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
This also affects F39, and it remains on F39: I can only open Google Maps with NoScript if all scripts of the domain are blocked. When I do so, I obviously get the google page that JavaScript needs to be enabled for this service. If I then enable/allow Google Map's domains, Firefox freezes shortly later. Even if I close firefox, the process of the one tab "Isolated Web Co" remains active on 100% CPU. I need to kill it manually. Vice versa, I can keep firefox open and just kill the damaged process. Then Firefox tells me the tab has crashed, but Firefox itself keeps working. Since I have not used such pages for several days, I can only say for sure that the issue started to occur either on firefox-119.0.1-1.fc39 or firefox-120.0-2.fc39. I use F39 KDE. The issue occurs with 6.5.X and 6.6.X kernels. However, I experienced that pages where google maps is integrated tend to work fine. E.g., when opening https://www.homegate.ch , entering some city and then opening offers in the map, it clearly uses Google Maps (through maps.googleapis.com & gstatic.com scripts) and it works always fine there. The actual "Google Maps" https://www.google.com/maps works never. The issue is now consistent: a page works always, or never (and if it breaks, it breaks always at the same time). See also my posts in https://bodhi.fedoraproject.org/updates/FEDORA-2023-528e17adf5 and https://bodhi.fedoraproject.org/updates/FEDORA-2023-2bd5892754 and https://bodhi.fedoraproject.org/updates/FEDORA-2023-dce9c4b01f
In bodhi, BZ#2251202 is only related to F37 - I just saw that this is maybe a mistake?
(In reply to Christopher Klooz from comment #19) > This also affects F39, and it remains on F39: > > I can only open Google Maps with NoScript if all scripts of the domain are > blocked. When I do so, I obviously get the google page that JavaScript needs > to be enabled for this service. If I then enable/allow Google Map's domains, > Firefox freezes shortly later. Even if I close firefox, the process of the > one tab "Isolated Web Co" remains active on 100% CPU. I need to kill it > manually. Vice versa, I can keep firefox open and just kill the damaged > process. Then Firefox tells me the tab has crashed, but Firefox itself keeps > working. > > Since I have not used such pages for several days, I can only say for sure > that the issue started to occur either on firefox-119.0.1-1.fc39 or > firefox-120.0-2.fc39. I use F39 KDE. The issue occurs with 6.5.X and 6.6.X > kernels. > > However, I experienced that pages where google maps is integrated tend to > work fine. E.g., when opening https://www.homegate.ch , entering some city > and then opening offers in the map, it clearly uses Google Maps (through > maps.googleapis.com & gstatic.com scripts) and it works always fine there. > The actual "Google Maps" https://www.google.com/maps works never. > > The issue is now consistent: a page works always, or never (and if it > breaks, it breaks always at the same time). > > See also my posts in > https://bodhi.fedoraproject.org/updates/FEDORA-2023-528e17adf5 and > https://bodhi.fedoraproject.org/updates/FEDORA-2023-2bd5892754 and > https://bodhi.fedoraproject.org/updates/FEDORA-2023-dce9c4b01f Hi Christopher, Can you confirm that you're still seeing this on firefox-120.0-3.fc39.x86_64 ? It's the -3 which has the recent fix in. If you're still seeing it on -3, can you please try flipping the about:config entry 'privacy.resistFingerprinting.randomDataOnCanvasExtract' to false and say if that fixes it?
Hi David, I was still on the *-2 build. I somehow have overseen that *-3 is already in bodhi for F39 (just had the one for F37 in the list). Maybe I set the filter not appropriately or so. Anyway, I just updated and checked firefox-120.0-3.fc39.x86_64 -> it works fine and solves the issue. Sorry, my bad ;)
Christopher: Thanks for confirming. Bug is still squashed!
Thanks for taking care ;)
FEDORA-2023-083a5e41cd has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-083a5e41cd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-083a5e41cd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-083a5e41cd has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.