| Summary: | totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | El jinete sin cabeza <romanescu.2019> |
| Component: | GLX | Assignee: | mesa-dev |
| Status: | RESOLVED NOTOURBUG | QA Contact: | mesa-dev |
| Severity: | normal | ||
| Priority: | medium | CC: | eero.t.tamminen, romanescu.2019 |
| Version: | 18.0 | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://launchpad.net/bugs/1758287 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
El jinete sin cabeza
2019-04-16 17:06:03 UTC
Which exact Mesa/GLX version has this been tested with? (In reply to Andre Klapper from comment #1) > Which exact Mesa/GLX version has this been tested with? Apparently "libgl1-mesa-glx 18.0.0~rc5-1ubuntu1" up. Since there are also reports in the Ubuntu Disco version. The first report in Ubuntu with this error was using 'libgl1-mesa-glx 18.0.0~rc5-1ubuntu1'. But then new reports of totem appeared that fail in the same. The latest version of Ubuntu (Disco Dingo 19.04) also crashes with the updated mesa package. The version of mesa: '18.0.0~rc5-1ubuntu1' was obtained by reviewing the parent report of launchpad.net. Specifically in https://bugs.launchpad.net/bugs/1758287 in the attached file 'Dependencies.txt' of that report. If you need any other information, please just let them know. I will try to help as much as I can. More about the package mesa: https://launchpad.net/ubuntu/+source/mesa The last version of the package mesa that occurs the crash is: libglx-mesa0 19.0.0-1ubuntu1 This I know because I reviewed the last duplicate report: https://bugs.launchpad.net/bugs/1821051 in this report I also checked 'Dependencies.txt' and found that the version. 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().
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.