Thanks. I think these are most relevant here:
- "Error 0x300d reported by eglSwapBuffers"
- "meta_onscreen_native_swap_buffers_with_damage failed. Frame aborted."
Error 0x300d is EGL_BAD_SURFACE, but the "surface" only gets created at
startup and maybe when monitors are hotplugged or resume from sleep. So
I suspect the real issue is that the system ran out of VRAM before then,
also suggested by:
- "failed to allocate NVKMS memory for GEM object"
It is suspicious that gnome-shell is being blamed for most of it, but
not definitive because gnome-shell also acts on behalf of apps. Still,
it's not OK that gnome-shell can't survive low memory situations, as
already tracked by bug 2154202. This bug can stay separate though, in
case there is a leak in gnome-shell itself as the numbers suggest.
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154316
Title:
GNOME Shell Wayland NVIDIA lock screen recovery fails with
gbm_surface_lock_front_buffer and high gnome-shell GPU memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2154316/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
