FrMo
commented
11 years ago Hello alextricity, Thank you for this interesting problem report.
There are actually two known "lock-up" problems that have been fixed in the current development branch already; but I have observed them only on "slow graphics hardware" (i.e. intel coreI5 build-in graphics).
Before we go to the console log (stdout.txt), could you check if one of these workarounds fix your problem:
- edit gravit.cfg, and set "recordingvideorefreshtime 0" (original value is 30). reason: gravit is regularly refreshing the display (OSD) during a spawn operation.It sometimes happens that the videoupdate is so slow, that it happens too often (basially, after each new particle). recordingvideorefreshtime 0 disables this feature.
- edit gravit.cfg, and add the following line: "particlesizemax 63" reason: the default value in gravit 0.5.0 is much too big; when particles are very near (=big), you graphics card can take up to several seconds to draw video frames with big particles.
Please tell us if one of these has solved the problem, or not.
cheers, Frank.
alextricity
Screensaver locks up after a period of time. Happens with the latest version on all computers. The systems have plenty of resources too. Overall, the systems are reliable.
The screensaver works great with pretty much any settings, but when it sits for a little while, the particles disappear and the program becomes unresponsive. Using only one core, and little memory it still happens. I suspect that maybe there is a scheduler thread AND computation thread running on the same core?.. the scheduler cant keep up and panics/dies/particles disappear. Does Gravit save logs?