[Suslik]

So I'm making an animation that's about 130 frames long under windows(i'm currently at windows 10, but it seemed to be the same under 7 and 8). It does process the first ~50 frames correctly and paraview.exe consumes about 1-1.5Gb of RAM at this point without any major fluctuations or steady increase. And then suddenly in matter of seconds memory consumption spikes to 13Gb, my machine runs out of memory and paraview crashes miserably with bad_alloc exception.

It is an old problem because it happened in previous versions as well but I managed to somehow work around this problem before(changing video size, frame skip, etc). However now nothing seems to work and it reliably crashes.

Dataset I'm working on is about 2Gb so posting it does not seem like a bright idea. But the problem is not related to this particular dataset because it happened a lot before with different datasets as well.

I've tried googling some workarounds that suggested turning off geometry caching but it was already turned off(probably from previous attempts). Turning on/off compression seems irrelevant as well.

At this point I just need a workaround to make the video. Does anyone have a piece of advice what to try?

[Suslik]

Ok it turned out that the problem is not with video, but with image saving routine as well. If I try to export animation as a sequence of images it gets stuck around the same frame as when I'm exporting a video(around frame 50-70, number seems to depend on image resolution).

So at least I've come up with a workaround: if I cannot process the whole video, I'll make a sequence of 60-70 images, crash and then make the rest 50-60(I have 120 all in all). Then I'll combine them into a video with a third party tool like VirtualDub.