MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011163ParaViewBugpublic2010-08-23 15:092010-09-15 19:48
ReporterAlan Scott 
Assigned ToDavid Partyka 
PriorityurgentSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.8.1Fixed in Version 
Project
Topic Name
Type
Summary0011163: ParaView crashes always SSH'ing into a mesa build
DescriptionParaView 3.8.1, as of Friday 8/20.

Cygwin, ssh -X into a Linux box. From there, do a client/server connect to a mesa build. It will crash when it tries to start up.

I get the following output:
pvserver: main/renderbuffer.c:1924: _mesa_add_renderbuffer: Assertion `bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL || fb->Attachment[bufferName].Renderbuffer == ((void *)0)' failed.
[rs1749:21412] *** Process received signal ***

This is using Mesa-7.8.2, although I don't expect it to change for other versions of ParaView.

The free world as we know it today won't end if this doesn't get fixed, but it would be a REALLY NICE THING TO HAVE for 3.8.1.

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
duplicate of 0010900closed François Bertel VTK offscreen context seg-faults with Mesa 7.8.2 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-08-23 15:09Alan ScottNew Issue
2010-08-23 16:28David PartykaStatusbacklog => tabled
2010-08-23 16:28David PartykaAssigned To => David Partyka
2010-08-24 16:17David PartykaNote Added: 0021931
2010-08-24 16:18David PartykaNote Edited: 0021931
2010-08-24 17:07David PartykaNote Added: 0021934
2010-08-31 09:34Utkarsh AyachitNote Added: 0022017
2010-08-31 09:34Utkarsh AyachitRelationship addedduplicate of 0010900
2010-08-31 09:34Utkarsh AyachitDuplicate ID0 => 10900
2010-08-31 09:34Utkarsh AyachitStatustabled => @80@
2010-08-31 09:34Utkarsh AyachitResolutionopen => fixed
2010-09-15 19:48Alan ScottNote Added: 0022244
2010-09-15 19:48Alan ScottStatus@80@ => closed

Notes
(0021931)
David Partyka   
2010-08-24 16:17   
(edited on: 2010-08-24 16:18)
Confirmed. Providing the backtrace. Note that I did this all on one machine instead of Alan's use case of running pvserver on a 3rd machine. Also --use-offscreen-rendering is required to reproduce.

(gdb) bt
#0 0x00007fffeb62fa75 in raise () from /lib/libc.so.6
#1 0x00007fffeb6335c0 in abort () from /lib/libc.so.6
#2 0x00007fffeb628941 in __assert_fail () from /lib/libc.so.6
#3 0x00007fffeacc2e4c in _mesa_add_renderbuffer (fb=0xbb95c0, bufferName=<value optimized out>, rb=0xbddd80) at main/renderbuffer.c:1922
#4 0x00007fffeac7b5dd in OSMesaMakeCurrent (osmesa=0xb69730, buffer=0x7fffe734f010, type=<value optimized out>, width=1299, height=<value optimized out>) at osmesa.c:1332
#5 0x00007fffef4e6687 in vtkXOpenGLRenderWindow::MakeCurrent (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1318
#6 0x00007fffef4e587a in vtkXOpenGLRenderWindow::CreateOffScreenWindow (this=0xb29c80, width=1299, height=926)
    at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:940
#7 0x00007fffef4e5d7d in vtkXOpenGLRenderWindow::Initialize (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1066
#8 0x00007fffef4e6183 in vtkXOpenGLRenderWindow::Start (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1185
0000009 0x00007fffef3a168f in vtkRenderWindow::DoStereoRender (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkRenderWindow.cxx:687
#10 0x00007fffef3a1660 in vtkRenderWindow::DoFDRender (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkRenderWindow.cxx:676
0000011 0x00007fffef3a1117 in vtkRenderWindow::DoAARender (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkRenderWindow.cxx:563
#12 0x00007fffef3a06ed in vtkRenderWindow::Render (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkRenderWindow.cxx:376
#13 0x00007fffef4e8ba5 in vtkXOpenGLRenderWindow::Render (this=0xb29c80) at /home/partyd/Kitware/ParaView/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1845
#14 0x00007ffff0b65071 in vtkParallelRenderManager::RenderRMI (this=0xb1d890) at /home/partyd/Kitware/ParaView/src/VTK/Parallel/vtkParallelRenderManager.cxx:756
#15 0x00007ffff75ee7d2 in vtkPVClientServerRenderManager::RenderRMI (this=0xb1d890) at /home/partyd/Kitware/ParaView/src/Servers/Filters/vtkPVClientServerRenderManager.h:55
#16 0x00007ffff75ed56b in RenderRMI (arg=0xb1d890) at /home/partyd/Kitware/ParaView/src/Servers/Filters/vtkPVClientServerRenderManager.cxx:57
#17 0x00007ffff0a851c8 in vtkMultiProcessController::ProcessRMI (this=0xb18200, remoteProcessId=1, arg=0x0, argLength=0, rmiTag=34532)
    at /home/partyd/Kitware/ParaView/src/VTK/Parallel/vtkMultiProcessController.cxx:636
#18 0x00007ffff0a85004 in vtkMultiProcessController::ProcessRMIs (this=0xb18200, reportErrors=0, dont_loop=1)
    at /home/partyd/Kitware/ParaView/src/VTK/Parallel/vtkMultiProcessController.cxx:600
#19 0x00007ffff7b62c4a in vtkRemoteConnection::ProcessCommunication (this=0xb098e0) at /home/partyd/Kitware/ParaView/src/Servers/Common/vtkRemoteConnection.cxx:74
#20 0x00007ffff7aeb17a in vtkProcessModuleConnectionManager::MonitorConnections (this=0x97c710, msec=0)
    at /home/partyd/Kitware/ParaView/src/Servers/Common/vtkProcessModuleConnectionManager.cxx:435
#21 0x00007ffff7af40b6 in vtkProcessModule::StartServer (this=0x64e630, msec=0) at /home/partyd/Kitware/ParaView/src/Servers/Common/vtkProcessModule.cxx:446
#22 0x00007ffff7af3b31 in vtkProcessModule::Start (this=0x64e630, argc=1, argv=0x64c8d0) at /home/partyd/Kitware/ParaView/src/Servers/Common/vtkProcessModule.cxx:357
#23 0x00007ffff763f39b in vtkPVMain::Run (this=0x64c3f0, options=0x64c140) at /home/partyd/Kitware/ParaView/src/Servers/Filters/vtkPVMain.cxx:276
#24 0x00000000004012cf in main (argc=2, argv=0x7fffffffe678) at /home/partyd/Kitware/ParaView/src/Servers/Executables/pvserver.cxx:45
(0021934)
David Partyka   
2010-08-24 17:07   
This apparently is a Mesa bug. MakeCurrent() is recreating the render buffer each time it is called. The second time it is called in vtkXOpenGLRenderWindow it crashes. A bug report will be filed with the Mesa developers.
(0022017)
Utkarsh Ayachit   
2010-08-31 09:34   
Mesa bug.
(0022244)
Alan Scott   
2010-09-15 19:48   
Agreed, this is a Mesa bug.

Successful compiles are done using the Mesa from Kitware.