Last active
December 22, 2015 16:58
-
-
Save falkreon/6502448 to your computer and use it in GitHub Desktop.
CookieClicker black-screen bug findings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I get the black screen consistently, BUT I've done some poking around with | |
Chrome's developer console. Everything's dead in the vm: | |
> Game | |
> Game.goldenCookie; | |
> Document | |
> echo("TEST"); | |
> | |
no response from any of that, not even an undefined or an error. | |
In other news, the network log: | |
main.js line 941: GET smallCookies.png stalls forever at Pending | |
main.js line 2058: GET cursor.png stalls forever at Pending | |
main.js line 2059: GET infoBG.png stalls forever at Pending | |
This is after loading 36 consecutive files with 200 OK's (not counting about:blank x3) | |
Chrome's Task Manager suggests that the Cookie Clicker tab is consuming | |
100% CPU (which it thankfully isn't because of Chrome's sandboxing. The | |
system is still responsive but none of the links on the page will hover | |
or respond). The memory footprint is at 872MB and *growing*. | |
The profiler told an interesting story. Over half the cycles were spent | |
on Document.addChild, and the other half was on GC. | |
Part of this strange circumstance is that a local copy does NOT have anything | |
of the sort. My guess is that it's a race condition about adding document | |
elements before the cursor loads, somehow causing an infinite loop of adding | |
elements. Then again, I could be completely wrong. I hope this data helps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment