Oi!

Last week i quit my 2 months-lasting break from VO coming up with my brandnew Ubuntu Feisty.
Now I always experience the problem that after five to fifteen minutes of playing my HD starts going crazy causing VO to not react anymore (which is quite awful while inflight, heh)
The only way then is to hard-reset my comp.
Maybe someone has got that issue as well and/or knows how to deal with it.

Thx in advance,
Mr Hanky's Cousin.

hmm... sounds very odd, can you still ctrl-alt-backspace once this happens?

try starting VO and just sitting in the station for a few minutes while you ctrl-alt-f2 to a console and run "top"... if it is in fact a leak of some sort you should see the vendetta process start consuming more and more resources (stay in top until you're sure the problem isn't happening) - if it doesn't recur, then try taking missions, jumping elsewhere, etc., until you can find out what activity is causing the problem..

...am I being clear enough?

Had this issue myself once (I think) or at least it sounds like the issue I was having. It turned out some process related to the Gnome WM was hanging, and not VO. One way of seeing if you are having the same problem I was is by exiting Gnome, and start VO using a clean X session xinit/xterm. If VO does not hang, then you have the same issue I did, I did resolve it in the end, (I think I degraded the app that was crashing) but cannot remember how.

this is happening to me right now i start vo and it uses 200MB
and 30 minutes later its using 650MB of my 768.

Agreed spidey, after like 15-30 minutes of flying (just hanging around in a station won't produce the problem) I am completely out of memory.
What I noticed:
Briefly before that occurs, the loading of the sector I jump to already takes a while. When I'm fast enough I can hope I make it to a station before the computer stops reacting on my input. After like 30-40 seconds the only way I can interact with my machine is to push the power button 4 secs to hard-reset it ;)

is this with pre-caching on or off?

nono, pre-caching is off. That was my first thought ;)

ok im messing with seting up a slackware box to run a bot off of, its an old machine so i decided to go with fluxbox to leave as much power as possible for vo, however it appears that 320mb of ram isn't enough let alone 256. is there any solution besides more ram?

it wold also probably help if i ran something faster than a p2 400mhz, but it still shouldent take that much ram

top - 21:31:30 up 59 min, 3 users, load average: 1.00, 1.02, 0.81
Tasks: 64 total, 3 running, 61 sleeping, 0 stopped, 0 zombie
Cpu(s): 98.5%us, 1.5%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 315428k total, 310648k used, 4780k free, 164k buffers
Swap: 1004020k total, 268600k used, 735420k free, 23968k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3368 root 25 0 87900 33m 2192 R 93.5 10.8 14:46.03 X
3380 max 16 0 472m 235m 4088 S 6.0 76.3 1:03.70 vendetta
3372 root 15 0 2304 684 532 R 1.0 0.2 0:05.49 top

You can try setting the texture quality to Lowest. That should use up less RAM.

already there, might simply be the 16mb video card isn't up to the task, though that shouldn't cause it to eat system ram, only run at a low framerate.

2.6.23.1 kernel seems to have fixed it a little
now it eats about 256mb total all the cpu but what can you expect from a 400mhz p2