Google maps dragging is very slow
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: nick_di, Unassigned)
Details
(Whiteboard: [platform-rel-Google][platform-rel-GoogleMaps])
Attachments
(2 files)
Comment 2•13 years ago
|
||
Comment 6•9 years ago
|
||
Updated•9 years ago
|
Updated•9 years ago
|
Yup, suppper slowwwwww. Still is using Firefox 74, under Linux (Linux Mint XFCE). Using AMD videocard with built-in AMDGPU kernel module driver for AMD.
Hardware acceleration enabled.
Same thing over here - 2017 MBP with two TB ports. This wasn't as much of an issue using Firefox on a 1080p screen, but moving up to a HiDPI 4K monitor the panning performance is extremely poor. Doing anything in Google Maps drops frames.
Comparing to Chromium browsers the panning performance there is significantly better.
Comment 10•5 years ago
|
||
I have the same issue. Ryzen 7 1700, RX 5700 XT, 16GB RAM, 4K display. Literally any Linux distribution I've tried has this issue. Linux Mint 20, Ubuntu 20.04, Fedora 32, Arch Linux. It's so bad that sometimes when I pan it literally just crashes my whole computer and I have to restart. In Chrome, panning works fine. I also have similar issues with Google Slides - the transitions are incredibly laggy, you can barely see them. This issue doesn't happen, however, in Windows, and macOS (Hackintosh). Very disappointing.
Comment 11•5 years ago
|
||
Same for me on Arch Linux with Nvidia GTX 1060 and proprietary drivers.
Comment 12•5 years ago
|
||
I would think the original reports were not using 4K.
André, can you reproduce with your distro?
Comment 13•4 years ago
|
||
lolrepeatlol are you still able to reproduce?
Comment 14•4 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #13)
lolrepeatlol are you still able to reproduce?
Sorry for the late response.
I had this issue quite a while ago and it was unbearable -- I had to open Chrome to use Google Maps. At times, if I used Maps in Firefox for too long, my computer would freeze and I would need to restart.
Fortunately, the issue has seemingly gotten a lot better on Fedora 35, but it's still not quite as smooth as Chrome. When I first open Maps on Firefox, there's some visible choppiness, but nothing terrible. Chrome doesn't have this choppiness. Overall I also noticed that Chrome feels like it's a consistent 60fps while Firefox feels like it's more at 30-40 fps. Still, it's a huge improvement over what it was at that time, and it's very usable nowadays.
I'm on Fedora 35 (using X11) and have noticed the same behavior on both Firefox 96 as well as Nightly 98 (2022-01-21).
Updated•3 years ago
|
Comment 15•3 years ago
|
||
Clear needinfos that are pending on inactive users.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Comment 16•3 years ago
|
||
Unable to reproduce in current versions.
Description
•