15 replies to this topic

[Annozero]

Hi, I have found that I cannot select "very big" or "giant" in the random maps size menu. If I do, after the loading screen the game returns to the main menu. In the log there is:
ERROR: JavaScript error: out of memory
ERROR: JavaScript error: Argument must be an object
ERROR: CMapReader::ParseTerrain() failed to get 'tileData' property

Thanks

[k776]

Yes, the map was too big, and your computer doesn't have enough RAM to generate it the game hasn't set aside enough memory to generate it.

What are your computer specs?

We should probably add limits so this type of thing doesn't happen.

[historic_bruno]

k776, on 21 June 2011 - 01:19 AM, said:

Yes, the map was too big, and your computer doesn't have enough RAM to generate it.

I don't think it has to do with RAM but rather the amount of memory set aside for random map scripting (which is hard coded to something like 96MB right now).

[Annozero]

I have 8Gb of RAM, so I don't think I'm running out of memory . I'm on amd64 if that makes a difference.

[historic_bruno]

Does it always fail to generate a very large or giant map, or only occasionally?

[Annozero]

historic_bruno, on 22 June 2011 - 12:27 AM, said:

Does it always fail to generate a very large or giant map, or only occasionally?

100% of times so far; I've also tried with different maps.

[historic_bruno]

That's odd, it seems to always work for me. I also have 8GB RAM on a 64-bit system. Which version of the game are you playing?

[wrod]

i had that problem too but idc cuz i dont play random maps

[Mythos_Ruler]

Is it possible that the random map generation process is taking more than 96MB of RAM, and therefor causing an error?

[Rasunadon]

I tried all sizes and no crash occured. It was only a bit slow. (IIANM: 2GB RAM on 32 bit Ubuntu)

[Annozero]

historic_bruno, on 22 June 2011 - 08:56 PM, said:

That's odd, it seems to always work for me. I also have 8GB RAM on a 64-bit system. Which version of the game are you playing?

I'm using the latest development version (0ad.dev ppa) on Kubuntu 11.04. Is there anything I can try (like a setting to allow more than 96 mb of ram)? In the settings I've changed the lodbias to the value suggested in the comment to make the graphics sharper (-1.5), but reverting the change doesn't fix the problem.

Edited by Annozero, 23 June 2011 - 10:51 AM.

[historic_bruno]

Annozero, on 23 June 2011 - 10:37 AM, said:

I'm using the latest development version (0ad.dev ppa) on Kubuntu 11.04. Is there anything I can try (like a setting to allow more than 96 mb of ram)?

If you'd like to try compiling the source code yourself, the constant RMS_RUNTIME_SIZE is defined in \source\graphics\MapGenerator.cpp. Otherwise, I can try gradually increasing the limit but you'd have to wait for the next dev package to test whether it works or not.

[Annozero]

historic_bruno, on 23 June 2011 - 09:09 PM, said:

If you'd like to try compiling the source code yourself, the constant RMS_RUNTIME_SIZE is defined in \source\graphics\MapGenerator.cpp. Otherwise, I can try gradually increasing the limit but you'd have to wait for the next dev package to test whether it works or not.

Thanks for the input. I downloaded the source from svn, updated that value up to 256 Mb, then 512 Mb, then 1 Gb and rebuilt every time, but nothing changes. Maybe I have to change also something else?

[historic_bruno]

Annozero, on 25 June 2011 - 08:16 PM, said:

Thanks for the input. I downloaded the source from svn, updated that value up to 256 Mb, then 512 Mb, then 1 Gb and rebuilt every time, but nothing changes. Maybe I have to change also something else?

Are you using 32-bit or 64-bit Kubuntu?

[historic_bruno]

Thanks to Philip, we've discovered the memory error is not occurring in the map generator context, but when the data is returned - so changing that constant wouldn't help. I'm guessing you use a 64-bit build of 0AD on 64-bit Linux, because Philip was able to reproduce this (I was not, I only have a 32-bit build on 64-bit Windows).

I've committed some changes to reduce the size of the random map data. Try the latest revision (r9664) and let us know how it works

[Annozero]

historic_bruno, on 26 June 2011 - 03:05 AM, said:

Thanks to Philip, we've discovered the memory error is not occurring in the map generator context, but when the data is returned - so changing that constant wouldn't help. I'm guessing you use a 64-bit build of 0AD on 64-bit Linux, because Philip was able to reproduce this (I was not, I only have a 32-bit build on 64-bit Windows).

I've committed some changes to reduce the size of the random map data. Try the latest revision (r9664) and let us know how it works

Yep! It works perfectly now, and it also seems faster at generating the map.Yes, I'm using an amd64 build on an amd64 system.Thanks!