View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0015780ParaView(No Category)public2015-10-14 11:042015-10-14 12:27
ReporterChristopher Neal 
Assigned ToAlan Scott 
PriorityurgentSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.3 
Target VersionFixed in Version 
Summary0015780: Paraview Crashes when loading state and trying to save an animation
DescriptionHello,

I have an Ensight Gold format data set that contains files for a set of timesteps. I have no issues with loading the data and performing a set of pipeline operations on the data. I saved my pipeline state to save time when loading other data sets that would require the same operations. The state file saves without an issue. When I open up paraview 4.3.1 again and load state I get a dialog box that asks me for the path to the ensight data file. I give it a path to a particular data set and it loads. It doesn't seem to be loading the other timesteps when it loads from the state file. When I try to save an animation it crashes before I can see anything on the error terminal. I'm running on Windows 7 64 bit.

Note: I also tried it with Paraview 4.4.0 and it still isn't loading the timesteps correctly when loading the ensight data set from the state file.

I have attached a minimal working example that has 3 timesteps worth of data and the state file that I used when it crashed.

It is somewhat important because it will be tedious to have to perform the pipeline operations for every data set that I want to animate.

Thank you,
Chris Neal
TagsNo tags attached.
ProjectTBD
Topic Name
Typecrash
Attached Fileszip file icon jetl_ensight_State_Crash_Test.zip [^] (3,545,783 bytes) 2015-10-14 11:04

 Relationships

  Notes
(0035285)
Christopher Neal (reporter)
2015-10-14 11:20

Update: I re-made the entire pipeline in Paraview4.4.0 and saved a state file. Upon doing that it looks to be working just fine now. I guess the trouble was in the format that the state file was being written in version 4.3.0.

For anyone having a similar issue the solution is to re-do your pipeline in 4.4.0 or greater and save the state from that version.

I'm not sure how to close a ticket.
(0035287)
Alan Scott (manager)
2015-10-14 12:27

Sounds like an error on the customers side. Thanks for reporting the bug, and even more so that the issue went away with a new build of ParaView.

Closing bug.

 Issue History
Date Modified Username Field Change
2015-10-14 11:04 Christopher Neal New Issue
2015-10-14 11:04 Christopher Neal Assigned To => Alan Scott
2015-10-14 11:04 Christopher Neal File Added: jetl_ensight_State_Crash_Test.zip
2015-10-14 11:20 Christopher Neal Note Added: 0035285
2015-10-14 12:27 Alan Scott Note Added: 0035287
2015-10-14 12:27 Alan Scott Status backlog => closed
2015-10-14 12:27 Alan Scott Resolution open => fixed


Copyright © 2000 - 2018 MantisBT Team