context.drawImage() slows down massively when drawing a few large images in a batch
Reported by
jer...@duckware.com,
Jan 23 2017
|
||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. visit vsynctester.com 2. click on gear icon 3. set 'background images' to 30 MP What is the expected behavior? browser should not slow down What went wrong? browser slows down massively Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0 See issue 464835
,
Jan 24 2017
,
Jan 24 2017
junov@: Could you please take a look into this if it can be merged into Issue 683994.
,
Jan 24 2017
It has the same title, but it is a separate use case and I have not verified that the root cause is identical.
,
Jan 25 2017
Thanks for the update. jerryj@/junov@ : Could you please help providing more description to differentiate good and Bad from Chrome TE side. Was unable to find the VSYNC word being either red or syan, its flickering continuously and looks grey on Win 10 using stable 55.0.2883.87 and canary 58.0.2991.0.
,
Jan 25 2017
durga.behera@, the bug is well known, as well as the solution. See https://bugs.chromium.org/p/chromium/issues/detail?id=464835#c33. Are you testing on intel integrated graphics systems? Attached is what I see. Massive slow down once memory for images goes beyond a limit.
,
Jan 27 2017
TE, I believe this will manifest more rapidly on a low-GPU memory device. Hence the suggestion in comment #6 to use an integrated graphics devices.
,
Jan 27 2017
,
Feb 28 2017
Still waiting on Bisect.
,
Mar 6 2017
,
Apr 13 2017
I can't repro this anymore. And we did fix things related to this. Still looking into the VSYNC issue, but this one seems to be ok. Please reopen if it's still happening.
,
Apr 13 2017
fs/11: undo 'Fixed'. The problem has not been fixed.
,
Apr 14 2017
,
Apr 18 2017
,
May 24 2017
Able to reproduce the issue on Windows-10 using chrome stable version 58.0.3029.110 and canary 60.0.3108.0 with the steps mentioned in comment#0. This is non-regression issue, observed from M30 #30.0.1599.92 and confirming the issue for further investigation. Thanks..
,
May 24 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 21 2018
,
Jul 25
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by chrishtr@chromium.org
, Jan 23 2017