[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] context loss, slowdowns and aw-snap dialogs



On Tue, May 19, 2015 at 12:11 AM, Kenneth Russell <kbr@google.com> wrote:
Concrete suggestions and code snippets which could improve browsers' behavior are welcome, as are suggestions on the reporting mechanisms browsers should ask from graphics drivers during low-memory and out-of-memory situations.
There's UA specific behavior that should be unified, such as: 
  • crashing the GPU process on an allocation triggered context loss but not issuing an out of memory error (chrome linux)
  • not issuing either a context loss nor issuing an out of memory error (firefox, chrome osx)
  • not issuing a context loss but issuing an out of memory error (chrome android, ios mobile safari)
  • not reloading the page on out of memory error (android)
  • reloading the page on out of memory error (ios)
Even if you can't improve upon the allocation situation, consistent behavior would at least go some way to get a consistent user experience.