This happens with Version 79.0.3945.79 (Official Build) (64-bit) on an Nvidia Optimus laptop (Dell G3) if I leave it turned on over night. I get tons of these strings in my ~/.xsession-errors:
[3617:3617:1224/030223.965361:ERROR:gles2_cmd_decoder.cc(3977)] ContextResult::kFatalFailure: Could not allocate offscreen buffer storage.
[3617:3617:1224/030223.966221:ERROR:gles2_cmd_decoder.cc(5780)] GLES2DecoderImpl::ResizeOffscreenFramebuffer failed because offscreen FBO was incomplete.
I always find my laptop using 100% CPU on at least one core (used by Chrome) just before I unlock my desktop (all fans making noise). It can be checked before unlocking either by logging in remotely over SSH or by switching to the text console VTY. Chrome magically stops consuming CPU and writing these log messages right after I unlock the desktop.
It also would eat few gigabytes of disk space each night with these messages, sometimes using all available disk space.
This happens with Version 79.0.3945.79 (Official Build) (64-bit) on an Nvidia Optimus laptop (Dell G3) if I leave it turned on over night. I get tons of these strings in my ~/.xsession-errors:
[3617:3617: 1224/030223. 965361: ERROR:gles2_ cmd_decoder. cc(3977) ] ContextResult: :kFatalFailure: Could not allocate offscreen buffer storage. 1224/030223. 966221: ERROR:gles2_ cmd_decoder. cc(5780) ] GLES2DecoderImp l::ResizeOffscr eenFramebuffer failed because offscreen FBO was incomplete.
[3617:3617:
I always find my laptop using 100% CPU on at least one core (used by Chrome) just before I unlock my desktop (all fans making noise). It can be checked before unlocking either by logging in remotely over SSH or by switching to the text console VTY. Chrome magically stops consuming CPU and writing these log messages right after I unlock the desktop.
It also would eat few gigabytes of disk space each night with these messages, sometimes using all available disk space.
I'm using xfce btw, not sure if it's important.