Hi Paul, Thanks for your hint, but I do have enough disk space (~10 GB). I've already tried to look in /var/log/ but didn't really find anything suspicious.
The strange thing is that it never happened with 3.6.2 or 3.6.1. The problem started to appear as of 3.7 (which I compiled from source) and remains also for 3.8 RC2 too Josef From: Paul McIntosh [mailto:[email protected]] Sent: Thursday, May 13, 2010 1:23 PM To: 'Josef Dubsky' Subject: RE: [Paraview] Paraview 3.8 RC2 makes the whole X restart A thought - do you have enough disk space? I am using 3.8 RC1/2 on Centos 5.5 with no issues. However I have noticed that if you run out of disk space, you get no warning and the session just crashes. Maybe ParaView is generating some file (swap?) that pushes your system to the limit of disk. I am not sure how to debug ParaView (yet) so I don't know if there is anything in the /var/log directory to look for. Paul _____ From: [email protected] [mailto:[email protected]] On Behalf Of Josef Dubsky Sent: Thursday, 13 May 2010 8:37 PM To: [email protected] Subject: [Paraview] Paraview 3.8 RC2 makes the whole X restart Dear all, I have the following problem with Paraview 3.8 RC2. Actually the problem already appeared with the version 3.7 which I built from source. However, as it was a development version, I thought there might be still some bugs. But the 3.8 RC2 which I've installed just today behaves the same. So the problem is the following: After a few minutes (can really reach from ~30 seconds to ~20 minutes) of working with Paraview suddenly my whole Linux session restarts and I have to login again. Of course by this I lose all the opened applications (not just Paraview), which is pretty bad. There's no real way, how to exactly reproduce the problem. I mean the time when the crash occurs seems more or less random. But after max ~30 mins of working with Paraview, you can be almost sure it crashes. The only thing I can say is, that if I just leave Paraview minimized and do something else, the crash doesn't occur. Thus it really happens only if you actively do something in Paraview. I'm using CentOS 5.5. Are there any logs or error messages you could help to analyze the situation more? I'm not sure where I could find something relevant. Regards Josef
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
