Bug 63472 - OSMesa Gallium Segfault in VTK Test
Summary: OSMesa Gallium Segfault in VTK Test
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/OSMesa (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-12 14:18 UTC by Kevin Hobbs
Modified: 2019-09-18 20:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
gdb backtrace of segfaulting test (5.54 KB, text/plain)
2013-04-12 14:18 UTC, Kevin Hobbs 		Details
valgring output (9.74 KB, text/plain)
2013-04-20 20:19 UTC, Kevin Hobbs 		Details
View All

Description Kevin Hobbs 2013-04-12 14:18:28 UTC 
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.
Comment 1 Brian Paul 2013-04-20 18:36:55 UTC 
Could you run this test with valgrind?  That should give us a bit more info.
Comment 2 Kevin Hobbs 2013-04-20 20:19:15 UTC 
Created attachment 78281 [details]
valgring output
Comment 3 GitLab Migration User 2019-09-18 20:12:29 UTC 
-- 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.