It looks like Canary dramatically improves things (from 40 seconds to 2-3 seconds), but still not as fast as IE/FF.

FWIW, on nVidia GeForce 750 Ti 2GB here (gaming-wise it's low-end) there's no difference between Chrome versions, all take a second or less to complete the action so I would guess the reported problem is caused by the Intel hardware/drivers (notoriously buggy since forever), which is handled or circumvented better in other browsers.

Actually bug is caused by Chrome's limited use of GPU memory (a couple years ago it was around 96MB max regardless of actual GPU memory available).  As long as an image fit in that buffer, everything was fast.  The moment an image was larger than the amount of GPU memory that Chrome is willing to use, things go south, very fast.

I was told (for years) that long-planned changes for improving how Chrome manages GPU memory has been in the works, and maybe those changes finally landed??

Can someone with knowledge comment on this -- did gpu memory handling changes land, or is this improvement caused by something else?

jerryj@ Thanks for the issue.

Tested this issue on Windows 10 on the reported version 63.0.3239.132, latest Stable 64.0.3282.186 and Canary 66.0.3356.0 and unable to reproduce the issue by following the steps mentioned above.

On navigating to the given URL, and clicking on "16291 x 2957" 'pano to view' link, can observe that the image is loaded in few seconds.
The same behavior is observed in Firefox and IE.
Attached is the screen cast and the chrome://gpu details for reference.

Request you to upgrade chrome to the latest version, retry the issue on a new profile without any flags/extensions and update the thread with the observations.

Thanks..

Deleted: 816310.mp4 4.1 MB

	816310.mp4 4.1 MB View Download

Deleted: gpu-M63.html 107 KB

gpu-M63.html 107 KB View Download

Susan, invalid test.  Issue was reported against Intel integrated graphics and you used NVIDIA.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

If you examine the F12 console, there is a timing diagnostic displayed.  This is what I see on my test system using various browsers, after clicking on the '16291 x 2957' link:

Firefox (60.0a1) - livingroom16291.jpg Tx204 in 152ms
Firefox (58.0.2) - livingroom16291.jpg Tx204 in 219ms
Internet Explorer (11) - livingroom16291.jpg Tx204 in 302ms
Canary (66.0.3357.0) - livingroom16291.jpg Tx204 in 1471ms
Chrome (64.0.3282.186) - livingroom16291.jpg Tx204 in 37582ms

Clearly, there was some change in Canary that is a major improvement over Chrome, but there is still room for a lot of improvement just to get 'on par' with the speed of other web browsers.

Sounds like a canvas issue. I'm not sure if we have concrete plans to improve this further in the short term.