On Sat, 2011-07-30 at 09:53 -0500, Kairhos wrote: > @hotshotkev: I use an x86 kernel for the same reason. > > @Martin Gregorie: > This is the output of top when Drakensang crashes and throws an out of memory error (I only included the first three processes as all other processes use less than 1% of memory at that time): > > > Tasks: 110 total, 1 running, 108 sleeping, 0 stopped, 1 zombie > Cpu(s): 0.7%us, 0.8%sy, 0.0%ni, 98.5%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st > Mem: 4147096k total, 3537336k used, 609760k free, 31700k buffers > Swap: 1959892k total, 0k used, 1959892k free, 1957400k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 4632 melvin 20 0 2992m 1.3g 49m S 2 34.0 4:20.98 drakensang.exe > 4635 melvin 20 0 6108 3200 684 S 1 0.1 0:05.56 wineserver > 2848 root 20 0 72940 56m 14m S 1 1.4 2:13.54 Xorg > > That points the finger squarely at drakensang as the memory hog. I seem to remember a comment about some Windows programs crashing by grabbing as much memory as possible whether they need it or not and then complaining because they can't get any more, so have a trawl through the forum archives to see which programs or groups of do this and what work-rounds there are. If you're running a 32 bit system, this looks very much like the program almost filling the user process space (3GB limit) and then crashing when it asks for another chunk of memory. Martin
