https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143 https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 ** Description changed: - https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 + https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 (DUPLICATE OF https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 ) https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG) https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 --- Backtrace goes through: totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError) Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects. In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code: --------------------------- if (gc) { /* Attempt to bind the context. We do this before mucking with * gc and __glXSetCurrentContext to properly handle our state in * case of an error. * * If an error occurs, set the Null context since we've already * blown away our old context. The caller is responsible for * figuring out how to handle setting a valid context. */ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) { __glXSetCurrentContextNull(); __glXUnlock(); __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent, False); return GL_FALSE; } --------------------------- I.e. bug is in what is given to Mesa, not what Mesa does. -> NOTOURBUG To me it looks something that could happen when Totem is exiting, gst- vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent(). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** No longer affects: gstreamer ** Also affects: totem via https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 Importance: Unknown Status: Unknown ** Description changed: - https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 (DUPLICATE OF https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 ) + https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE OF: + https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 + https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG) https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 --- Backtrace goes through: totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError) Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects. In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code: --------------------------- if (gc) { /* Attempt to bind the context. We do this before mucking with * gc and __glXSetCurrentContext to properly handle our state in * case of an error. * * If an error occurs, set the Null context since we've already * blown away our old context. The caller is responsible for * figuring out how to handle setting a valid context. */ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) { __glXSetCurrentContextNull(); __glXUnlock(); __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent, False); return GL_FALSE; } --------------------------- I.e. bug is in what is given to Mesa, not what Mesa does. -> NOTOURBUG To me it looks something that could happen when Totem is exiting, gst- vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent(). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in Totem: Unknown Status in gstreamer-vaapi package in Ubuntu: New Status in mesa package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE OF: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG) https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 --- Backtrace goes through: totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError) Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects. In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code: --------------------------- if (gc) { /* Attempt to bind the context. We do this before mucking with * gc and __glXSetCurrentContext to properly handle our state in * case of an error. * * If an error occurs, set the Null context since we've already * blown away our old context. The caller is responsible for * figuring out how to handle setting a valid context. */ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) { __glXSetCurrentContextNull(); __glXUnlock(); __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent, False); return GL_FALSE; } --------------------------- I.e. bug is in what is given to Mesa, not what Mesa does. -> NOTOURBUG To me it looks something that could happen when Totem is exiting, gst- vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent(). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
