Need a way to debug WebGL related browser crashes
Reported by
andreas....@gmail.com,
Dec 18 2016
|
||||
Issue descriptionSteps to reproduce the problem: This is a request for a better way to debug crashes in WebGL based web applications. I think it would be better if the browser threw an Exception in JavaScript with details about the error, rather than the "Aw snap" screen. I'm working on developing a WebGL version of the open source game Freeciv, which is available on https://play.freeciv.org/ The game works nicely on mobile devices with 3GB or more of RAM. On devices with 2GB of RAM, the browser tab will crash and just give the "Aw snap" error message. 1. Go to https://play.freeciv.org/ with Chrome on Android device with 2GB of RAM. 2. Click Single-player 3D Beta button. 3. Fill in name and click start game. 4. Then the browser tab will crash with the "Aw snap" error message. How can I find out more about debugging this WebGL related problem? What is the expected behavior? I need more information from the browser about the cause of the crash. Therefore throwing a JavaScript exception would help. What went wrong? How can I debug this problem? Did this work before? N/A Chrome version: 56 Channel: stable OS Version: 7 Flash Version:
,
Dec 20 2016
It's likely that these crashes are caused by out-of-memory errors. Do you have any crash IDs in about:crashes so we can confirm? For security reasons, it's longstanding Chrome behavior that any OOM will crash the process, rather than allowing null pointers to flow throughout the system. It's impossible to patch all of the allocation sites in Blink to cause them to generate a JavaScript exception upon OOM. Have you used the memory profiler in DevTools to see where Freeciv's allocations are going? Maybe you can reduce its memory consumption. 2 gigabytes seems excessive.
,
Jan 23 2017
Hi, andreas.rosdal@gmail.com Could you try the advice from comment #2? Thank you!
,
Jan 23 2017
Hi! Feel free to close this issue. I have reduced the memory usage of the game, and it doesn't crash as frequently any more. Thanks!
,
Jan 23 2017
Thanks for letting us know. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tkent@chromium.org
, Dec 18 2016