"Context3D not available" on Chrome OS
We have suddenly seen a dramatic increase on fatal Starling errors "Context3D not available" on Chrome OS devices (as of last Friday).
Someone else reported similar findings and Josh Tynjala was able to reproduce the issue on his Asus Chromebit.
Just wanted to bring this into attention of Adobe, more about it here:
https://forum.starling-framework.org/topic/context3d-not-available-on-chrome-os-since-yesterday
