I have recently been trying the multithreaded linux64 build of spring on an Intel I7 with 8 gigs of ram. At what seem to be random times, in about 20% of the games, spring will freeze, the memory usage shoots up and the system becomes unusable.
I can see the memory usage go up from about 1 gig to 8 gig in 2 or 3 seconds in a taskbar widget. Then i have a few seconds in which it will be possible to kill the spring process, and if I don't, the system becomes unusable with heavy thrashing and swap usage.
The problem does not happen with the single threaded version. The binaries are from the ubuntu ppa repository.
Spring MT linux64 crashes with memory usage spike
Moderator: Moderators
- sillynanny
- Posts: 125
- Joined: 20 Jun 2008, 14:26
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Spring MT linux64 crashes with memory usage spike
MT is completely broken for everything except BA atm. Don't use it.
- sillynanny
- Posts: 125
- Joined: 20 Jun 2008, 14:26
Re: Spring MT linux64 crashes with memory usage spike
Just for reference, I was playing BA.
Re: Spring MT linux64 crashes with memory usage spike
Forbs comment wasn't very helpful :)
MT is completely untested with 64 bit. I'm surprised it even started.
I don't have a 64bit os installed, so cannot help atm. Sorry
If you could attach a debugger and halt the exe when the problem occurs, maybe you could get a stack trace.
MT is completely untested with 64 bit. I'm surprised it even started.
I don't have a 64bit os installed, so cannot help atm. Sorry

If you could attach a debugger and halt the exe when the problem occurs, maybe you could get a stack trace.
- sillynanny
- Posts: 125
- Joined: 20 Jun 2008, 14:26
Re: Spring MT linux64 crashes with memory usage spike
zerver, if you have a 64 bit capable CPU you can install a 64 bit OS under Virtualbox even if your host OS is 32bit.
About the stack trace, if you can post instructions on what to do, I could try. I am familiar with the command line stuffs, I just need to do how to invoke the debugger and how to obtain the stack trace. This might be tricky because memory usage shoots up quickly and I will have only a few seconds to get the trace saved to disk before it all goes down thrashing.
About the stack trace, if you can post instructions on what to do, I could try. I am familiar with the command line stuffs, I just need to do how to invoke the debugger and how to obtain the stack trace. This might be tricky because memory usage shoots up quickly and I will have only a few seconds to get the trace saved to disk before it all goes down thrashing.