| Summary: | OSMesa Gallium Segfault in VTK Test | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Kevin Hobbs <hobbsk> |
| Component: | Drivers/OSMesa | Assignee: | mesa-dev |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
gdb backtrace of segfaulting test
valgring output |
||
Could you run this test with valgrind? That should give us a bit more info. Created attachment 78281 [details]
valgring output
-- 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/876. |
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.
Created attachment 77885 [details] gdb backtrace of segfaulting test Since OSMesa Switched to Gallium The VTK test : vtkRenderingVolumePython-cursor3D has been segfaulting on one of the two machines which run the test with OSMesa from git. I ran the test in gdb and got the backtrace in the attached vtk_osmesa_backtrace.txt On a hunch I tried setting breakpoints at cso_release_all and vtkOSOpenGLRenderWindow::DestroyOffScreenWindow but they are entered only once.