[Paraview] Volume Rendering Crash

Greer, Cody cody.greer at wustl.edu
Thu Sep 5 13:26:49 EDT 2013


Thank you Mark.  I checked and the stack size limit was already pretty high, but I set it to unlimited anyway.  Unfortunately I'm still getting the same crashing behavior.  I also just installed Paraview on a windows computer and I have the same problem.  Rendering works very well when I set the VOI up to about half the full volume size.  Any higher than that and Paraview crashes instantly.  The crash details show (not surprisingly) that the fault module is vtkRenderingVolume-pv4.0.dll.  Does anyone have any other ideas?

Thanks,
Cody

________________________________
From: Vanmoer, Mark W <mvanmoer at illinois.edu>
Sent: Friday, August 30, 2013 3:46 PM
To: Greer, Cody; paraview at paraview.org
Subject: RE: Volume Rendering Crash

Hi Cody,

I've had a similar experience and it was because I had a limited stack size in the shell I was launching paraview from. Try checking ulimit -a

Hope that helps,
Mark

From: paraview-bounces at paraview.org [mailto:paraview-bounces at paraview.org] On Behalf Of Greer, Cody
Sent: Friday, August 30, 2013 2:23 PM
To: paraview at paraview.org
Subject: [Paraview] Volume Rendering Crash

Dear Paraview Community,

I am volume rendering a 2560 x 2160 x 200 image stack that totals 2 GB in size.  The stack loads fine, Paraview consistently crashes when I try to render the whole volume.  The data is represented as a uniform grid.  I don't think this is a memory issue.  I have monitored memory usage during crashes and the system always has at least 29 GB of free memory when it crashes.  The behavior is the same regardless of which rendering algorithm I choose (smart, ray cast, texture mapping, GPU).  I have tried loading the data in both RAW format and NRRD format with no luck.  I am using the Linux 64 bit binary installation from the Paraview website.  My desktop is running CentOS.

I'd appreciate any advice you might have for me.

Thanks,
Cody
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130905/b792109f/attachment.htm>


More information about the ParaView mailing list