[http://sourceforge.net/p/ufoai/bugs/2760 Item 2760] imported from sourceforge.net tracker on 2013-01-28 19:47:16

UFO:AI ate all my memory on loading the following map:
CM_LoadMap: "-city/city +str_cross +strv_1 +str_cross +strv_2 +str_cross +strh_1 +bldl_4x4_2a +strh_2 +str_rail_cross +craft_drop_firebird +str_rail_cross +strv_rail_2a +str_rail_cross +craft_ufo_scout +strh_3" "-32 -40 0 -32 -32 0 -32 0 0 -32 8 0 -32 40 0 -24 -40 0 -24 -32 0 -24 0 0 8 -40 0 8 -32 0 8 0 0 8 8 0 8 40 0 -24 8 0 -24 40 0"

I have 1G system RAM + 2G swap. The kernel had to kill it:
[ 7154.075758] Out of memory: kill process 5066 (ufo) score 709275 or a child

-geever
===== Comments Ported from Sourceforge =====

====== geever (2011-01-01 11:20:29) ======

valgrind.log
====== geever (2011-01-01 11:22:04) ======

Tried to make a valgrind.log. I hit Ctrl+C before ufo was kicked out:

==5845== malloc/free: 487,265 allocs, 480,161 frees, 2,412,468,562 bytes allocated.

-geever
====== tlh2000 (2011-01-04 07:27:47) ======

backtrace
====== tlh2000 (2011-01-04 07:28:22) ======

the city maps where compiled with and without a lightmap - this might confuse the engine. see the attached backtrace geever was able to make
====== tlh2000 (2011-01-04 07:28:47) ======

as a sidenote - this does not happen on my machine with lightmaps compiled for +city
====== aduke1 (2011-11-25 23:17:46) ======

geever,

1. now that your old PC has finally given up, I suppose you can no longer reproduce this, correct ?
2. I could try on my EeePC, but +city is no longer part of master. Do you know of any decisions regarding +city (temporarily/permanently banned) ?
====== geever (2011-11-26 19:54:19) ======

True, I cannot reproduce it now, but it's most probably not because the issue was fixed... I don't know the plans about +city.

Reread the bug, I remember that the mapset wasn't "clean". Some map parts were downloaded from map-get repo, some others (probably due to the version mismatch issue) were compiled locally - those without lightmaps so I don't have to burn my CPU for hours.
However if this constellation confused the engine so much is a very serious problem I see that this is not a common situation, so I agree on decreasing bug priority.

-geever