I encountered (and reported to Chrome) the STATUS_BREAKPOINT error. In my case, I could actually see visual glitches (like black paint chips flickering) in the DOM page on the source. My solution was to filter things (especially special things) and try to interleave updates.
Multiple factors contributed to the overload:
- Sandbox development caused tab RAM to grow from 400MB to 4GB rapidly, via refresh of network resources.
- texture sample was complex: deep clone hierarchy, interactive listeners, and memory-critical prototype.
- requestAnimationFrame functions were not yet over-optimized to release memory or handle error bubbling of resource fragments.
- imports could be configured to convert a smaller filetype, or alternate imports could release memory better (in a loop).
- GPU paint layer was forcefully invoked
Your friend,
Vlad “Unfriendly” Vladovstok
BYOB… I opened your file. It is a square white plane. I had this knowledge prior to formulating a correspondence.