Reproducible segfault or freeze when saving animation from Paraview

[pffft!]

How to reproduce:

1) get Paraview from http://paraview.org/New/download.html

2) get test case from
http://rapidshare.com/files/75594165/test.tar.gz.html

3) File -> Load State, select test.pvsm

4) File -> Save Animation -> Boom!

With a 7600GS the X server segfaults (bug report #1), with a 8600GTS the machine freezes real hard (bug report #2).

[AaronP]

Thanks for reporting this, pffft!! I've managed to reproduce the problem and have filed bug 376572.

[pffft!]

169.07 fixes this for the 8600 GTS. For the 7600 GS, I can still make the X server segfault with this test case.

Edit: I retract this first statement. It only takes longer (in terms of animation frames) until the bug occurs.

[pffft!]

More info:

For the 8600 GTS, if I go from 10 to 100 frames in the example above, I get (specifically and only with 169.07!!) the following machine check events logged:

MCE 0
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 0 BANK 0 STATUS f200084000000800 MCGSTATUS 0
MCE 1
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 0 BANK 5 STATUS f200001014000e0f MCGSTATUS 0
MCE 2
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 1 BANK 5 STATUS f200001030000e0f MCGSTATUS 0
MCE 3
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 2 BANK 0 STATUS f200084000000800 MCGSTATUS 0
MCE 4
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 2 BANK 5 STATUS f200000014000e0f MCGSTATUS 0
MCE 5
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 3 BANK 5 STATUS f200000030000e0f MCGSTATUS 0

100% reproducible after about 40 frames. Yes I can read (*NOT* a software problem!), but I'm not really convinced. I have not yet tried to decode the numbers, but the only hit I get from google on f200001014000e0f indicates a bus problem. Maybe the new driver togehther with the GPU ****s up the PCI bus??

[zander]

Do you see any NVRM messages prior to the MCEs?

[pffft!]

None.

[AaronP]

Sorry for the slow update. I never could reproduce the MCE problem, but the X server crash issue should be fixed. Unfortunately, there's still a problem in OpenGL, but the good news is that you can work around it with the attached patch.

[pffft!]

Ok. Thanks for the workaround. I can now save animations.

[julianc]

I was referred to this thread from someone on the Paraview mailing list when I reported a similar problem with my computer freezing while saving a screenshot or animation. I have recently upgraded to Ubuntu 8.04 and the Nvidia 169.12 driver for my graphics card, which is a GeForce 6800 XT. This has improved the situation. I can now save several screenshots without a lockup, and the save animation feature in Paraview at least starts up and saves 12 to 15 frames. But then the machine does freeze up. I tried the glFinish patch noted in this thread, but it did not have any effect.

It seems that the only obvious difference is that I have an older GeForce card. Are there still relevant bugs remaining in the Nvidia 169.12 driver? Is there anything I can do in terms of configuration settings that would cure this problem? It is frustrating that I cannot produce the animations that I would like without wondering if my machine is going to crash.

[pffft!]

It is frustrating that I cannot produce the animations that I would like without wondering if my machine is going to crash.

Don't feel bad. It also doesn't really work for me. The animations I can produce with the posted patch contain occasional black frames and after an animation is saved, Paraview works as slow as molasses and has to be restarted. Unfortunately, Paraview's save-state functionality is also broken.

Tip: Use Windows for animations. There, it works.