# Paraview crashes when saving pngs from pvtp files

**URL:** https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074
**Category:** ParaView Support
**Created:** [June 18, 2019, 8:11pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074 "2019-06-18T20:11:39Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![wyan](https://discourse.paraview.org/user_avatar/discourse.paraview.org/wyan/32/1604_2.png) [@wyan](https://discourse.paraview.org/u/wyan)
#### Post date: [June 18, 2019, 8:11pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/1 "2019-06-18T20:11:39Z")

</div>

I have a series of parallel XML polyline files as (\*.pvtp and \*.vtp) files in base64 binary format (uncompressed) loaded into paraview. The visualization process works normally. However, when I try to save animation into a series of png files, paraview just crashes. Here is a bit more details:  
(1) Paraview 5.5.2 works fine for both visualization and png rendering  
(2) Paraview 5.6.0 crashes on pvtp files. But if I first convert all pvtp and vtp files into non-parallel vtp format or legacy vtk format in paraview and reload data, then png sequences can be rendered. There are still warnings like ‘missing View()’, but the pngs are normal  
(3) Paraview 5.6.1 crashes even if I convert the data into legacy vtk or non-parallel vtp format.  
(4) All crash cases can be reproduced on Windows10, macOS 10.14, CentOS 7.5 and Ubuntu 18.04. I also compiled paraview 5.6.0 from superbuild on Ubuntu18.04, and got the same problem.

Is there a workaround for this? The main motivation of using 5.6 is the new particle filter where particle trajectories can be easily visualized. Is there a way to use this feature back in 5.5.2?

Thank you,

---

<div class="post-metadata">

### Author: ![wyan](https://discourse.paraview.org/user_avatar/discourse.paraview.org/wyan/32/1604_2.png) [@wyan](https://discourse.paraview.org/u/wyan)
#### Post date: [June 18, 2019, 9:30pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/2 "2019-06-18T21:30:03Z")

</div>

Here is a group of example files that crashes Paraview 5.6.1. Every visualization functions work normally, but crashes when saving the animation into a sequence of png files.

The file is around 30MB and available on this dropbox link

> **[test.tar.xz](https://www.dropbox.com/s/kyih3eukwpu31tf/test.tar.xz?dl=0)**
>
> Shared with Dropbox

How to reproduce: use the pvsm file in this tar ball to load the 3 frame pvtp data files. Then in paraview do ‘File -\> save animations’, choose a png sequence.

Thanks,

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 19, 2019, 3:21am UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/3 "2019-06-19T03:21:09Z")

</div>

I confirmed the crash on ParaView 5.6.1 on macOS. However, on ParaView’s master branch, from which 5.7.0 will soon be produced, I cannot reproduce the crash. I opened an issue [here](https://gitlab.kitware.com/paraview/paraview/issues/19100), but unless someone else can reproduce on master, I will close the issue.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 19, 2019, 9:58am UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/4 "2019-06-19T09:58:51Z")

</div>

Unable to reproduce on ArchLinux with ParaView 5.6.1 binary release. Could you give exact steps to reproduce ?

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 19, 2019, 1:42pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/5 "2019-06-19T13:42:05Z")

</div>

> [@wyan](#):
>
> How to reproduce: use the pvsm file in this tar ball to load the 3 frame pvtp data files. Then in paraview do ‘File → save animations’, choose a png sequence.

Following those steps, I was able to reproduce the crash.

---

<div class="post-metadata">

### Author: ![wyan](https://discourse.paraview.org/user_avatar/discourse.paraview.org/wyan/32/1604_2.png) [@wyan](https://discourse.paraview.org/u/wyan)
#### Post date: [June 19, 2019, 2:09pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/6 "2019-06-19T14:09:24Z")

</div>

Thank you for confirming this! For now, is there a precompiled version of master-branch that I can use? Is there a rough timeline for next release?

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 19, 2019, 2:14pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/7 "2019-06-19T14:14:06Z")

</div>

Go to [www.paraview.org/download](http://www.paraview.org/download) and select “Nightly” from the popup menu with the versions.

 ![image](https://discourse.paraview.org/uploads/default/original/2X/2/2531436472af77a3da01d818ce5f816d36f69bb5.png)

5.7 should be out in about a month.

---

<div class="post-metadata">

### Author: ![wyan](https://discourse.paraview.org/user_avatar/discourse.paraview.org/wyan/32/1604_2.png) [@wyan](https://discourse.paraview.org/u/wyan)
#### Post date: [June 20, 2019, 1:59pm UTC](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074/8 "2019-06-20T13:59:46Z")

</div>

Thank you! I just tried this version and a sequence of 5000 pngs were generated without error or warnings. I will keep an eye on the release of 5.7.0.
