Firefox is slow or unresponsive when using street view on Google Maps
Categories
(Core :: Performance: General, defect)
Tracking
()
People
(Reporter: matt, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
Version: 105.0.1
Build ID: 20220923151236
Distribution ID: canonical-002
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0
OS: Linux 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022
OS Theme: Yaru / Yaru
Multiprocess Windows: 1/1
Fission Windows: 1/1 Enabled by default
Remote Processes: 12
Enterprise Policies: Inactive
Google Location Service Key: Found
Google Safebrowsing Key: Found
Mozilla Location Service Key: Found
Safe Mode: false
Memory Size (RAM): 31.2 GB
Disk Space Available: 206 GB
Steps to reproduce: Using Ubuntu 22.04, open native Firefox and go to Google Maps, drop pin on street to access street view and try to navigate in street view.
Actual results:
Actual results: Page freezes and unable to navigate. Will sometime become responsive after a minute or so.
Expected results:
Expected results: Being able to navigate on street view by clicking arrows on screen to move direction and zooming in and out by scrolling mouse.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Could you include a profile of this occurring on this bug? See https://profiler.firefox.com/ for instructions.
(In reply to Bas Schouten (:bas.schouten) from comment #2)
Could you include a profile of this occurring on this bug? See https://profiler.firefox.com/ for instructions.
Unfortunately, my system updated and I am now on 106.0 (64 bit) SNAP version in Ubuntu. The problem is no longer present in this version.
I will know to include a profile when I submit my next bug.
Comment 4•3 years ago
|
||
Thanks Matthew! Closing this, feel free to re-open if you run into this bug again.
Description
•