Opened 12 days ago

Last modified 11 days ago

#5645 new defect

JavaScript error: uncaught exception: out of memory

Reported by: sumpfralle Owned by:
Priority: Should Have Milestone: Backlog
Component: Core engine Keywords:
Cc: Patch:

Description

Approximately once every two hours I receive the following fatal error when running 0ad:

TIMER| common/modern/setup.xml: 199.223 us
TIMER| common/modern/styles.xml: 298.606 us
TIMER| common/modern/sprites.xml: 1.74399 ms
TIMER| common/setup.xml: 441.873 us
TIMER| common/sprites.xml: 654.179 us
TIMER| common/styles.xml: 166.043 us
TIMER| savegame/save.xml: 17.0087 ms
TIMER| GetSavedGames: 22.4247 ms
WARNING: JavaScript warning: gui/common/functions_utility_loadsave.js line 8
reference to undefined property metadata.mods
Saved game to '/home/lars/.local/share/0ad/saves/savegame-0038.0adsave'
ERROR: JavaScript error: uncaught exception: out of memory

Attached you find gdb's stack trace (with Debian's 0ad-dbgsym package installed) and my system_info.txt.

I am using a 32 bit system with 8 GB of RAM. Memory exhaustion does not seem to be relevant (even given the limit of 4 GB per process in a 32 bit system).

The error is not strictly reproducable and does not seem to depend on the map size or other memory-related circumstances. After loading a save game from a time shortly before a crash, the same game works flawlessly for some more hours.

The error even happens while the game is paused.

Attachments (2)

out-of-memory-stacktrace.txt (42.2 KB) - added by sumpfralle 12 days ago.
system_info.txt (6.1 KB) - added by sumpfralle 12 days ago.

Download all attachments as: .zip

Change History (3)

Changed 12 days ago by sumpfralle

Changed 12 days ago by sumpfralle

Attachment: system_info.txt added

comment:1 Changed 11 days ago by stanislas69

I usually can reproduce it playing Corinthian Ismuth (4) With four AIs (playing as observer) but I'm not sure whether it's a leak, or just the AIs being too greedy...

Note: See TracTickets for help on using tickets.