Issue metadata
Sign in to add a comment
|
cubeslam.com game unresponsive after first or second ball
Reported by
huape...@amazon.com,
Dec 1 2016
|
||||||||||||||||||
Issue descriptionChrome Version : latest master, v56 URLs (if applicable) : www.cubeslam.com What steps will reproduce the problem? (1) Go to the website play the game (2) after first ball, unresponsive game What is the expected result? the game is smooth What happens instead? unresponsive Please provide any additional information below. Attach a screenshot if possible. I cannot reproduce this on v53, v54
,
Dec 1 2016
Note that this issue started in v55.
,
Dec 1 2016
chrome-canary(57) seems to be working fine.
,
Dec 5 2016
Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 56.0.2924.14 and canary 57.0.2939.0.able to play the game without any issues. Please find the attached screen cast for the same. huapengl@could you please once try the issue on latest M56 dev build and update the thread if the issue still persists. Thanks,
,
Dec 5 2016
Please note that this issue was observed in Chrome for Android, not Desktop. Sorry for not mentioning this in the initial post. I'm not sure on any additional details (e.g. are all Nexus devices impacted or only some?) I'll let huapengl@ comment on that.
,
Dec 5 2016
This does seem to repro a lot on commit 001b8a3e1c50d1658419ef58993839c7c924d00e which is an lkgr slightly before the v56 branch point. I just confirmed that this does also repro in Chrome and Chromium 56.0.2924.13 In Chromium it took me 3 balls, in Chrome ~10 (Though I assume that was just random chance, I can't see how any proprietary Chrome code would impact this) However, I have so far been unable to reproduce this on a Nexus 7. My current guess would be that this could be a resource leak. The device type this was reproed on is on a lower price scale than a Nexus 7, and thus might be more heavily impacted by resource leaks.
,
Dec 6 2016
,
Dec 10 2016
What Android device and OS are you seeing this issue on?
,
Jan 9 2017
No feedback was received in the last 30 days from reporter "huapengl@amazon.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 1 2016