2025-07-18 05:29 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006035Spring engineGeneralpublic2018-09-01 18:25
ReporterFloris 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilitysometimes
StatusassignedResolutionreopened 
Product Version104.0 +git 
Target VersionFixed in Version104.0 +git 
Summary0006035: spring sometimes freezes when changing resolution ingame
Descriptionthe method when doing this is:
Spring.SendCommands("Fullscreen 1")
Spring.SetConfigInt("XResolutionWindowed", tonumber(resolutionX))
Spring.SetConfigInt("YResolutionWindowed", tonumber(resolutionY))
Spring.SendCommands("Fullscreen 0")
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0019313

Kloot (developer)

I assume by "freezes" you mean "hiccups" since infolog looks normal and hang detection was not triggered. even so, switching from 1920x1080 to 3840x2160 and back is never exactly fast because (amongst other things) various large buffers have to be instantaneously reallocated, including by {gad,wid}gets via the ViewResize callin.

currently the engine does not measure how long each part takes.

~0019314

Floris (reporter)

by freezes I didnt mean multiple occurences, just stays frozen.

see: https://www.youtube.com/watch?v=koa0NemSwvw

~0019315

Kloot (developer)

I'll add some logging code to narrow this down.

~0019316

Kloot (developer)

test 668-ge433d2a when it becomes available.

~0019317

Floris (reporter)

same thing happened, but this time i also tried manually giving the cmd /fullscreen when it froze. And that worked, until you ordered it to go windowed again, chaing resolution after didnt matter as well

~0019318

Kloot (developer)

Last edited: 2018-08-23 13:28

View 2 revisions

seems like something is causing the GL context to be destroyed.

does this also happen with native (WindowBorderless = 0) fullscreen mode?

~0019319

Floris (reporter)

yes

~0019320

Kloot (developer)

next candidate: 670-gc51c539

recreating the entire context would be extremely painful (to code) so please tell me this one works.

~0019321

Floris (reporter)

seems fixed now

~0019322

Kloot (developer)

ty

~0019332

Floris (reporter)

still happening :(

~0019334

Floris (reporter)

seems to only happen in windowed mode
+Notes

-Issue History
Date Modified Username Field Change
2018-08-22 17:08 Floris New Issue
2018-08-22 17:08 Floris File Added: infolog.txt
2018-08-22 20:20 Kloot Note Added: 0019313
2018-08-22 21:06 Floris Note Added: 0019314
2018-08-22 21:49 Kloot Note Added: 0019315
2018-08-22 23:08 Kloot Note Added: 0019316
2018-08-22 23:08 Kloot Status new => feedback
2018-08-23 12:10 Floris File Added: infolog-2.txt
2018-08-23 12:10 Floris Note Added: 0019317
2018-08-23 12:10 Floris Status feedback => new
2018-08-23 13:21 Kloot Note Added: 0019318
2018-08-23 13:25 Floris Note Added: 0019319
2018-08-23 13:28 Kloot Note Edited: 0019318 View Revisions
2018-08-23 20:55 Kloot Note Added: 0019320
2018-08-23 23:25 Floris Note Added: 0019321
2018-08-23 23:39 Kloot Assigned To => Kloot
2018-08-23 23:39 Kloot Status new => resolved
2018-08-23 23:39 Kloot Resolution open => fixed
2018-08-23 23:39 Kloot Fixed in Version => 104.0 +git
2018-08-23 23:39 Kloot Note Added: 0019322
2018-09-01 17:26 Floris Status resolved => feedback
2018-09-01 17:26 Floris Resolution fixed => reopened
2018-09-01 17:26 Floris Note Added: 0019332
2018-09-01 18:25 Floris Note Added: 0019334
2018-09-01 18:25 Floris Status feedback => assigned
+Issue History