Summary: | Crash when creating new context after destroying the old one using indirect rendering | ||
---|---|---|---|
Product: | Mesa | Reporter: | Guilherme <gqmelo> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
Severity: | critical | ||
Priority: | medium | CC: | mforce2 |
Version: | 10.5 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=353763 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
VTK/Qt Python program that crashes
gdb stack trace xtrace with glx commands |
Description
Guilherme
2015-08-19 14:27:49 UTC
Created attachment 117784 [details]
gdb stack trace
Created attachment 117785 [details]
xtrace with glx commands
As the crash is a seg fault on update_framebuffer_size because surface=NULL, I tried to just make a check if the surface is NULL. Then it does not crash anywhere else, but nothing is rendered. Several similar crashes have been reported in KDE due to update_framebuffer_size() being called with surface=NULL during a call to st_Clear(). Happened to me with KDE too. Thread 1 (Thread 0x7f9b04e05800 (LWP 1082)): [KCrash Handler] #6 0x00007f9aea533a09 in update_framebuffer_state () from /usr/lib/dri/r600_dri.so #7 0x00007f9aea53282c in st_validate_state () from /usr/lib/dri/r600_dri.so #8 0x00007f9aea53a5d1 in st_Clear () from /usr/lib/dri/r600_dri.so #9 0x00007f9b14f8b156 in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/libQt5Quick.so.5 Is this working for you with recent Mesa? I was unable to figure out the examples dependences on my distro so couldn't test. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/991. |
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.