MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007301ParaView(No Category)public2008-07-07 19:002011-01-13 17:00
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PriorityhighSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.4Fixed in Version3.4 
Project
Topic Name
Type
Summary0007301: Screenshots of clip box are crashing ParaView
DescriptionThis only seems to happen when I am doing a clip to a box. Strange!

Client/multiple server

Wavelet, apply.
Clip/ Box. Change X to 0.9. Apply.

File/ Save Screenshot/ any file type (.jpg crashes).

Here is the error output:

ERROR: In C:\alan\paraviewNightlyTrunk\src\ParaView3\VTK\Rendering\vtkOpenGLRenderer.cxx, line 852
vtkOpenGLRenderer (09EA0D38): shader source compile error


ERROR: In C:\alan\paraviewNightlyTrunk\src\ParaView3\VTK\Rendering\vtkOpenGLRenderer.cxx, line 864
vtkOpenGLRenderer (09EA0D38): no log


ERROR: In C:\alan\paraviewNightlyTrunk\src\ParaView3\VTK\Rendering\vtkOpenGLRenderer.cxx, line 910
vtkOpenGLRenderer (09EA0D38): program link error


ERROR: In C:\alan\paraviewNightlyTrunk\src\ParaView3\VTK\Rendering\vtkOpenGLRenderer.cxx, line 924
vtkOpenGLRenderer (09EA0D38): no log:


Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.


Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-07-07 19:00Alan ScottNew Issue
2008-07-09 08:01Utkarsh AyachitStatusbacklog => tabled
2008-07-09 08:01Utkarsh AyachitAssigned To => Utkarsh Ayachit
2008-07-09 08:03Utkarsh AyachitAssigned ToUtkarsh Ayachit =>
2008-07-09 08:04Utkarsh AyachitNote Added: 0012666
2008-07-09 10:51Utkarsh AyachitAssigned To => Utkarsh Ayachit
2008-07-25 09:34Utkarsh AyachitStatustabled => @80@
2008-07-25 09:34Utkarsh AyachitResolutionopen => fixed
2008-07-25 09:34Utkarsh AyachitNote Added: 0012822
2008-07-28 19:16Alan ScottStatus@80@ => closed
2008-07-28 19:16Alan ScottNote Added: 0012844
2009-05-13 13:58Utkarsh AyachitTarget Version => 3.4
2009-05-13 13:59Utkarsh AyachitFixed in Version => 3.4
2011-01-13 17:00Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00Source_changeset_attached => VTK master 020ef709
2011-06-16 13:10Zack GalbreathCategory => (No Category)

Notes
(0012666)
Utkarsh Ayachit   
2008-07-09 08:04   
Actually...not that strange. I am guessing this has something to do with depth peeling being used with offscreen context (which is created for saving images). Depth peeling is being used since the box widget reports that it has translucent panels. Easy fix would be to disable translucency.
(0012822)
Utkarsh Ayachit   
2008-07-25 09:34   
When the faces are not selected, their opacity is 0. In
reality when opacity is 0, it should not affect the consideration if depth
peeling is used since it doesn't really matter. However, vtkActor::GetIsOpaque()
return false when opacity is 0, and we end up using depth peeling. The more
complete fix would need some change to the actor API. For now, simply not
considering the face into translucency check unless it is selected does the
trick.

/cvsroot/ParaView3/ParaView3/VTK/Widgets/vtkBoxRepresentation.cxx,v <-- VTK/Widgets/vtkBoxRepresentation.cxx
new revision: 1.7; previous revision: 1.6
(0012844)
Alan Scott   
2008-07-28 19:16   
Tested client/server