Issue metadata
Sign in to add a comment
|
JS Maps API maps freeze when zooming out |
||||||||||||||||||||||
Issue descriptionExample URL: https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple Steps to reproduce the problem: 1. Go to a JS Maps API map (the URL above) 2. Pinch to zoom out a few times 3. The display freezes. 4. Go to a different tab, then come back. 5. The map is unfrozen What is the expected behavior? What went wrong? Perhaps this is a rendering problem? Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Before the latest update in stable. Does this work in other browsers? Yes Chrome version: 49.0.2623.91 Channel: stable OS Version: 6.0.1 Flash Version: Shockwave Flash 21.0 r0 On this page, the map is in an iframe. Only the iframe freezes: https://developers.google.com/maps/documentation/javascript/examples/map-simple If you scroll down the page so the map isn't visible anymore, and scroll back, it's working again. On this site, the whole page freezes: https://www.commbank.com.au/personal/locate-us.html Not even a reload seems to fix it.
,
Mar 16 2016
,
Mar 16 2016
,
Mar 16 2016
,
Mar 16 2016
,
Mar 16 2016
,
Mar 16 2016
,
Mar 16 2016
My first guess was that this is crbug.com/591561 , but it seems not.
,
Mar 16 2016
(i.e. I tested with a fix to that bug and it does not fix this one) Vlad, Enne, any guesses? A bisect request is also in progress.
,
Mar 16 2016
Nothing comes to mind, sorry.
,
Mar 16 2016
Chatted with Vlad, he thinks its a bug in activation (pending tree->active tree in the compositor). Trying out that theory now with a hack.
,
Mar 16 2016
Confirmed that it is an activation bug. Looking further...
,
Mar 16 2016
+weiliangc. Wei any guesses?
,
Mar 16 2016
Removing Needs-Bisect until we have a desktop repro, Android has no bisect. Going to try a manual bisect.
,
Mar 16 2016
,
Mar 16 2016
We should push this fix to M49 stable.
,
Mar 16 2016
+kerz as FYI. We'll review and get back to you. Request a merge when you're comfortable with the fix and it's been exercised in canary please.
,
Mar 16 2016
And we should cherrypick to M50 beta as well :)
,
Mar 17 2016
,
Mar 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ad3070d0f8f9b7513222014d218d0937da6d8077 commit ad3070d0f8f9b7513222014d218d0937da6d8077 Author: vmpstr <vmpstr@chromium.org> Date: Thu Mar 17 00:46:00 2016 cc: Ensure to process active low res pending high res tilings at raster This patch ensures that we process active low res pending high res tilings, since they can have required for activation tiles. Previously, this only applied to non ideal tiles, but clearly it's possible to hit the rare case of low res on active while high res on pending. R=enne, chrishtr BUG= 595209 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1808043002 Cr-Commit-Position: refs/heads/master@{#381613} [modify] https://crrev.com/ad3070d0f8f9b7513222014d218d0937da6d8077/cc/tiles/tiling_set_raster_queue_all.cc
,
Mar 18 2016
,
Mar 18 2016
[Automated comment] Request affecting a post-stable build (M49), manual review required.
,
Mar 18 2016
Your change meets the bar and is auto-approved for M50 (branch: 2661)
,
Mar 18 2016
,
Mar 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c25b3f9fd96e6cb7fa82e6e0e1756077055b5564 commit c25b3f9fd96e6cb7fa82e6e0e1756077055b5564 Author: Alex Mineer <amineer@chromium.org> Date: Fri Mar 18 21:08:40 2016 cc: Ensure to process active low res pending high res tilings at raster This patch ensures that we process active low res pending high res tilings, since they can have required for activation tiles. Previously, this only applied to non ideal tiles, but clearly it's possible to hit the rare case of low res on active while high res on pending. R=enne, chrishtr BUG= 595209 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1808043002 (cherry picked from commit ad3070d0f8f9b7513222014d218d0937da6d8077) Cr-Original-Commit-Position: refs/heads/master@{#381613} Cr-Commit-Position: refs/branch-heads/2623@{#638} Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907} [modify] https://crrev.com/c25b3f9fd96e6cb7fa82e6e0e1756077055b5564/cc/tiles/tiling_set_raster_queue_all.cc
,
Mar 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/87f65d892f297bb6dcc12ee2653955fd14e9774e commit 87f65d892f297bb6dcc12ee2653955fd14e9774e Author: Vladimir Levin <vmpstr@chromium.org> Date: Fri Mar 18 22:29:23 2016 cc: Ensure to process active low res pending high res tilings at raster This patch ensures that we process active low res pending high res tilings, since they can have required for activation tiles. Previously, this only applied to non ideal tiles, but clearly it's possible to hit the rare case of low res on active while high res on pending. R=enne, chrishtr BUG= 595209 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1808043002 Cr-Commit-Position: refs/heads/master@{#381613} (cherry picked from commit ad3070d0f8f9b7513222014d218d0937da6d8077) Review URL: https://codereview.chromium.org/1817443004 . Cr-Commit-Position: refs/branch-heads/2661@{#288} Cr-Branched-From: ef6f6ae5e4c96622286b563658d5cd62a6cf1197-refs/heads/master@{#378081} [modify] https://crrev.com/87f65d892f297bb6dcc12ee2653955fd14e9774e/cc/tiles/tiling_set_raster_queue_all.cc
,
Mar 21 2016
Verified fix on 49.0.2623.105 / S6 Verizon / LMY47X.
,
Mar 23 2016
Verified fix in M50 - 50.0.2661.49 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted