User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3) Gecko/20100805 Firefox/4.0b3 Firefox/3.6.4 Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3) Gecko/20100805 Firefox/4.0b3 Whilst using satellite view in Google Maps to zoom in/out, Firefox will hang for about 30 seconds to 1 minute. CPU usage spikes during this time. After about 1 minute the map will display and Firefox becomes responsive again. Reproducible: Always Steps to Reproduce: 1. Open Google maps 2. Switch to satellite view 3. Zoom in or out Actual Results: Firefox hangs for up to 1 minute, map eventually displays and Firefox becomes responsive Expected Results: Firefox should not hang, map should display within a few seconds Also tested this on nightly build, same problem occurred. Mozilla/5.0 (Windows NT 6.1; rv:2.0b4pre) Gecko/20100809 Minefield/4.0b4pre - Build ID: 20100809040505 This is a regression since Firefox 4.0 beta 2
I confirmed: Regression Window: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5f857be14db9&tochange=b8b62b351c09 I guess landing of Bug 572520 causes the problem
I confirm this on Linux builds. All the same symptoms as Tony-E reported above. In addition, if one tries the 'drag' the window with the left mouse button held down in order to change the view field, the re-rendering takes longer to complete than expected from performance in Firefox 3.6.* builds and also during this time there are very high CPU spikes. In Linux process monitor (top) 'firefox-bin' has high CPU usage but it is 'X' that appears to be hogging the CPU with values of around 60-70% (this is in addition to the 30-40 % of 'firefox-bin'). I guess this effect will be more noticed in lower end or older hardware configurations.
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Component: General → ImageLib
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → imagelib
I'm hoping that this will be fixed by the patch over at bug 583028. Joe made some tryserver builds with that patch, though unfortunately it seems they didn't get built on windows for some reason. Can those of you experiencing this problem on linux and mac give this build a spin? http://firstname.lastname@example.org/
(In reply to comment #3) > I'm hoping that this will be fixed by the patch over at bug 583028. > > Joe made some tryserver builds with that patch, though unfortunately it seems > they didn't get built on windows for some reason. Can those of you experiencing > this problem on linux and mac give this build a spin? > > http://email@example.com/ I've just tried out that tryserver Linux build. That build works much better on the Google maps than the present 'trunk' builds. It is perhaps not quite as quick to finish rendering after dragging this image as with the 3.6.* builds, but much better and now quite usable.
Since the patch for bug 583028 landed on mozilla-central, Google Maps are working again. Rendering speed is similar to 3.6.8 builds. Tested on Windows.
(In reply to comment #5) > Since the patch for bug 583028 landed on mozilla-central, Google Maps are > working again. Rendering speed is similar to 3.6.8 builds. Tested on Windows. Awesome! Resolving fixed.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.