2021-02-25 23:47 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005986Spring engineGeneralpublic2020-07-04 16:36
Reporternixtux 
Assigned ToKloot 
PriorityhighSeverityminorReproducibilitysometimes
StatusresolvedResolutionfixed 
Product Version104.0 +git 
Target VersionFixed in Version104.0 +git 
Summary0005986: Crash on startup - terminate called after throwing an instance of 'std::bad_alloc'
DescriptionSemi random crash on startup with spring version 104.0.1-529-g00b43c96a maintenance (Debug)

Link to stacktrace https://pastebin.com/xwVqmPEu
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0019131

Kloot (developer)

Last edited: 2020-07-04 16:36

View 3 revisions

splashScreenFile="/home/nixtux/.config/spring/./texture.png"
bmp = {xsize = 4096, ysize = 4096, channels = 4, ...}


you have a 4K-resolution (64MB) splashscreen which eats up the texmempool.

in springsettings.cfg, set TextureMemPoolSize to a value greater than 64 or downsize this texture.

~0019133

nixtux (reporter)

Ah thanks, any chance of it failing graceful with a helpful error message to users?

~0019134

Kloot (developer)

will think about it, for now I'm just going to bump the pool size.
+Notes

-Issue History
Date Modified Username Field Change
2018-05-19 10:57 nixtux New Issue
2018-05-19 11:20 Kloot Note Added: 0019131
2018-05-19 11:22 Kloot Note Edited: 0019131 View Revisions
2018-05-19 12:33 nixtux Note Added: 0019133
2018-05-19 12:52 Kloot Note Added: 0019134
2018-05-19 13:18 Kloot Assigned To => Kloot
2018-05-19 13:18 Kloot Status new => resolved
2018-05-19 13:18 Kloot Resolution open => fixed
2018-05-19 13:18 Kloot Fixed in Version => 104.0 +git
2020-07-04 16:36 Kloot Note Edited: 0019131 View Revisions
+Issue History