Memory overrun bug with the Ship_Storage_Helper_0.20_2012.06

[Lestradae]

I am successfully playing Oolite with more than half a thousand oxps in ... and it is running fine on my system

The game needs about 1.7GB RAM to run in that state, it could go up to 3.5GB if it needed, but it never goes beyond 2GB RAM need.

When I put the Ship_Storage_Helper_0.20_2012.06.24.oxp in, though, I get a memory overrun where the game at start goes up and up until it hits the 3.5+GB RAM ceiling and crashes with a "game ended with unknown exception" or something like that without even reaching the spinning Cobra screen.

It is this oxp for sure, which also creates a problem for the Respray_for_Griffs_0.4_2012.06.24.oxp as this is dependent on ship storage oxp and therefore won't run either.

I am using Oolite version 1.77 as of the official release, not the trunk version. Haven't tested with that one. And I have a Windows 7 64bit system with 16GB RAM.

[Ironfist]

Lestradae,
Even though you have a 64 bit operating system, the current windows build is only a 32 bit program, this is because of some of the libraries that are used. This limits the program to the 2GB limit that you mention seeing and this cannot be exceeded. To use a 54 bit version of Oolite you would need to switch operating systems to something like Linux for which there are 64 bit builds.
I think basically there is little you can do except reduce the number of OXPs that you have.
I am sure if I am wrong someone will be along soon to correct this viewe.

Ironfist

[Thargoid]

Aside from wondering what a 54-bit version would look like, it sounds right to me.

[Ironfist]

Just because I am trying to eat and type at the same time.

Ironfist

[Smivs]

Just because I am trying to eat and type at the same time.

Ironfist

Let's hope the eating goes better than the typing, then

[pagroove]

I am successfully playing Oolite with more than half a thousand oxps in ...

That's the Lestradae I know. Always 'stretching' the system to its limits

[Ironfist]

The eating has finished. Not sure the typing is going to get a lot better.

Ironfist

[Eric Walch]

Even though you have a 64 bit operating system, the current windows build is only a 32 bit program, this is because of some of the libraries that are used. This limits the program to the 2GB limit that you mention seeing and this cannot be exceeded.

As I understood the current window builds use a special feature that allows to use 2 times 2GB = 4 GB. And that is consitent with Lestradae having 3.5 GB in use.

[Zieman]

Lestradae,
Even though you have a 64 bit operating system, the current windows build is only a 32 bit program, this is because of some of the libraries that are used. This limits the program to the 2GB limit that you mention seeing and this cannot be exceeded. To use a 54 bit version of Oolite you would need to switch operating systems to something like Linux for which there are 64 bit builds.
I think basically there is little you can do except reduce the number of OXPs that you have.
I am sure if I am wrong someone will be along soon to correct this viewe.

Ironfist

Oo-kay.
When I buy new computer to get most out of Elite: Dangerous, I hope that Windows build of Oolite will then be fully 64 bit. Or I'm going to ask for help on how to set up dual-boot Linux & Windows 7 box here.

[Lestradae]

No, seriously, this is something with the ship storage helper. With the 533 other oxps ... my game uses between 800MB and 1.8GB of RAM. (Experiments have shown that the system can handle up to about 3.5GB of Oolite without any problems!)

With the ship storage helper, RAM escalates up to 3.5+GB RAM - about 2GB more than usual! So this must be some memory overrun problem that this oxp runs into. I doubt one oxp eats as much as 533 others including all of Povray's planets

[pagroove]

Well I know that on Mac I cannot have all Povray Sets at the same time in my add on directory. I have 2 at max. One for the galaxy I'm in and one for the next.