Open Talisca opened 9 years ago
Hello, I'm glad you posted this. I have experienced exactly the same issue and thought my game was at fault. But it seems the error also appears from a completely blank cocos2d-js project.
To be clear: If you schedule updates, they run smoothly in the background. The actual rendering of the scene stops while you try to click/drag the mouse around, but if you, for example, put a console.log("foo") in a scheduled frame update, it will print out correctly 30/60/whatever times per second while the screen stays frozen.
No updates?
Update: only happens when framerate is set to 30 in project.json. 60 works fine
I've got a strange behavior in Chrome (47) in WebGL-Mode (Canvas is fine). The whole screen of the game freezes. The game itself runs smoothly (in the background..)
Steps to reproduce:
Tested in Windows 7 Windows 8 Windows 8.1 Windows 10 Debian 8
Browsers tested: Chrome (behavior as mentioned above) Opera (works fine) Firefox (works fine) Safari (works fine)
Frameworks tested: cocos2d-html5 3.3 cocos2d-html5 3.8