2025-07-21 19:27 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002436Spring engineGeneralpublic2011-05-28 01:33
Reporterabma 
Assigned ToKloot 
PrioritynormalSeveritycrashReproducibilityalways
StatusresolvedResolutionfixed 
Product Version0.82.7 
Target VersionFixed in Version0.82.7+git 
Summary0002436: OOM on game-loading with many cpu-cores
Descriptionwith 12 cores + 6 GB RAM a user seems to get crashes because of OOM (?)

http://springrts.com/phpbb/viewtopic.php?f=11&t=25047&p=486825#p486825

lowering HardwareThreadCount fixed the crashes


so, limit the count to threads depending on #cpu core, memory + map width + map height to avoid such crashes?
Additional Informationhttps://github.com/spring/spring/blob/master/rts/Sim/Path/Default/PathEstimator.cpp#L145
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0006672

Kloot (developer)

Being a 32-bit application Spring can never allocate more than 4GB of memory for itself, even if a machine has much more and/or runs a 64-bit OS. The real problem though is fragmentation. A map like Throne "only" requires ~100MB per CPathFinder instance, but getting N such blocks in a row is less likely as N becomes larger. For N=12, you're most often out of luck.
+Notes

-Issue History
Date Modified Username Field Change
2011-05-16 11:53 abma New Issue
2011-05-16 11:54 abma Summary OOM on game-start with many cpu-cores => OOM on game-loading with many cpu-cores
2011-05-16 11:55 abma Description Updated
2011-05-16 23:14 Kloot Status new => assigned
2011-05-16 23:14 Kloot Assigned To => Kloot
2011-05-28 01:33 Kloot Note Added: 0006672
2011-05-28 01:33 Kloot Status assigned => resolved
2011-05-28 01:33 Kloot Fixed in Version => 0.82.7+git
2011-05-28 01:33 Kloot Resolution open => fixed
+Issue History