2025-08-10 08:33 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004049Spring engineLuapublic2013-10-11 12:26
Reporterbaracoder 
Assigned ToKloot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
Product Version94.1 
Target VersionFixed in Version94.1.1+git 
Summary0004049: memory leak in luaui
DescriptionOn a long play of BA Chicken 3.05, my system froze up with all of 8BG RAM + swap full. I played with a friend, he had the same problem (his one was killed by oomkiller first), so its not host only.

I have tried to reproduce by starting a game with a few Shard AIs and pausing after one minute.

The memory usage continues to grow at about 0,5MB/s (but it jumps sometimes).
Disabling luaUI (/luaui disable) seams to stop it. I tried to disable widgets individually but had no success yet.

If I start and pause spring again and switch to an other desktop, the memory usage increases at about 20MB/s. This also stops when luaUI is disabled.

It reproduces with BA 7.83 too.
Steps To Reproduce1. start spring
2. pause spring
3. watch memory usage
4. /luaui disable
5. watch memory usage
Additional InformationSometimes see this message:

[f=0002442] Player paused the game
[f=0002442] Player Player went AFK
[f=0002442] Player Player came back
[f=0002442] Warning: [Watchdog] Hang detection triggered for Spring 94.1 (ASIM GML OMP).
[f=0002442] Warning: MT with 8 threads.
[f=0002442] Warning: (in thread: main)
[f=0002442] Error: Stacktrace (main):
[f=0002442] Error: (Note: This stacktrace is not 100% accurate! It just gives an impression.)
[f=0002442] Error: Unable to create stacktrace
[f=0002442] Error: Stacktrace (sim):
[f=0002442] Error: No Stacktraces for non-MainThread.
[f=0002442] Error: Stacktrace (audio):
[f=0002442] Error: No Stacktraces for non-MainThread.



~/.spring/script.txt
[GAME]
{
    HostIP=;
    HostPort=8452;
    IsHost=1;
    MyPlayerName=Player;

    ModHash=4162646679;
    MapHash=1146365237;
    Mapname=Charlie in the Hills v2.1;
    GameType=Balanced Annihilation V7.83;

    startpostype=3;
    [mapoptions]
    {
    }
    [modoptions]
    {
        relayhoststartpostype=3;
        disablemapdamage=0;
        fixedallies=0;
        ghostedbuildings=1;
        limitdgun=0;
        mo_allowfactionchange=1;
        mo_combomb_full_damage=0;
        mo_comgate=0;
        mo_coop=1;
        mo_enemypushing=0;
        mo_enemywrecks=1;
        mo_greenfields=0;
        mo_no_close_spawns=1;
        mo_noowner=0;
        mo_noshare=1;
        mo_nowrecks=0;
        mo_preventdraw=0;
        mo_progmines=0;
        mo_startpoint_assist=0;
        shareddynamicalliancevictory=0;
        maxspeed=3;
        maxunits=500;
        minspeed=0.3;
        mo_armageddontime=0;
        startenergy=1000;
        startmetal=1000;
        deathmode=com;
        mo_storageowner=team;
        mo_transportenemy=all;
        movetype=normal;
        pathfinder=normal;
        teamdeathmode=allyzerounits;
    }
    NumRestrictions=0;
    [RESTRICT]
    {
    }

    NumPlayers=1;
    NumUsers=2;

    [PLAYER1]
    {
        Name=Player;
        CountryCode=;
        Spectator=0;
        Rank=0;
        IsFromDemo=0;
        Team=1;
    }
    [AI0]
    {
        Name=Bot1;
        ShortName=Shard;
        Version=dev;
        Team=0;
        IsFromDemo=0;
        Host=1;
        [Options]
        {
        }
    }

    [TEAM0]
    {
        TeamLeader=1;
        StartPosX=4080;
        StartPosZ=6799;
        AllyTeam=1;
        RGBColor=0.976471 1 0;
        Side=ARM;
        Handicap=0;
    }
    [TEAM1]
    {
        TeamLeader=1;
        StartPosX=4080;
        StartPosZ=1425;
        AllyTeam=0;
        RGBColor=0 0 0;
        Side=ARM;
        Handicap=0;
    }

    [ALLYTEAM1]
    {
        NumAllies=0;
    }
    [ALLYTEAM0]
    {
        NumAllies=0;
    }
}

TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0011739

Kloot (developer)

known bug, disable any widgets that call GetVisible{Units,Features}
+Notes

-Issue History
Date Modified Username Field Change
2013-10-11 11:57 baracoder New Issue
2013-10-11 12:26 Kloot Note Added: 0011739
2013-10-11 12:26 Kloot Status new => closed
2013-10-11 12:26 Kloot Assigned To => Kloot
2013-10-11 12:26 Kloot Resolution open => fixed
2013-10-11 12:26 Kloot Fixed in Version => 94.1.1+git
+Issue History