2025-06-14 04:53 CEST
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006077Spring engineGeneralpublic2018-11-12 05:492020-07-08 20:08
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeveritycrashReproducibilityalways
StatusresolvedResolutionfixed 
Product Version104.0 +git 
Target VersionFixed in Version104.0 +git 
Summary0006077: 104.0.1-888-g15d6cc6 maintenance crash at exit with -107374181 / 0xC0000005L / STATUS_ACCESS_VIOLATION
DescriptionEvery time I close Spring the zk wrapper detects that Spring sent an exit code indicating a crash, hang, or some other problem. The issue appears to occur consistently over many ways of closing Spring.

In the linked crash report I launch spring with the test version of zkmenu, then click the Exit button (which does Spring.Quit()). See: https://github.com/ZeroK-RTS/CrashReports/issues/16691
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
related to 0006398closed 104.0.1-1510-g89bb8e3 maintenance Crash on game load with twitch studio beta 
+Relationships

-Notes

~0019522

Google_Frog (reporter)

2018-11-12 08:24

 I also had players reporting that windows told them "Spring has crashed" every time they closed Spring. I don't know how this relates to crash reports because MP testing does not use the wrapper in the same way.

~0019523

abma (administrator)

2018-11-12 10:57

 Zero-K.exe Warning: 0 : Spring exit code is: -1073741819, assuming crash

-> -107374181 -> 0xC0000005L -> STATUS_ACCESS_VIOLATION

~0019524

Google_Frog (reporter)

2018-11-12 13:10

 The ticket name is now misleading, as I do not know whether Spring always returns this particular exit code.

~0019525

Google_Frog (reporter)

2018-11-12 13:11

 The name change is fine, just be aware of the claim that I am not making.

~0019526

abma (administrator)

2018-11-12 13:12

 the crash should be fixed at least: when its fixed the other error codes can be checked / tested / ... whatever.

~0019527

Anonymous (viewer)

2018-11-12 13:24

 Fix 4ed0b9e11a99cdacc0378c9c8be95d3e91be4fd5 committed to develop branch: fix 0006077, repo: spring changeset id: 11128

~0019528

Anonymous (viewer)

2018-11-12 13:24

 Fix 0871f35da2ffdaaf528105c5b3ad320f74d237f9 committed to maintenance branch: fix 0006077, repo: spring changeset id: 11129

~0019529

Kloot (developer)

2018-11-12 13:35

 the set of candidates for a traceless post-main crash after loading just a LuaMenu and exiting is pretty small, fixed w.h.p.

~0019532

Google_Frog (reporter)

2018-11-13 03:15

 The error with this exit code is not resolved. https://github.com/ZeroK-RTS/CrashReports/issues/16722

~0019533

Kloot (developer)

2018-11-13 11:09

 get me a stacktrace.

~0019534

Google_Frog (reporter)

2018-11-13 12:46

 I start zkmenu, click Exit. The infolog that you see above is all I have. How do I make Spring give me a stacktrace?

~0019535

Google_Frog (reporter)

2018-11-13 13:09

 I bisected to the limit of my stored engines:

Bug:
104.0.1-781-g80f9374 https://github.com/ZeroK-RTS/CrashReports/issues/16730
104.0.1-567-gc484c10 https://github.com/ZeroK-RTS/CrashReports/issues/16731
104.0.1-527-gf2536df https://github.com/ZeroK-RTS/CrashReports/issues/16732

Works:
104.0.1-409-g07c2800

Broken in some other way:
104.0.1-616-g52f5f2b

~0019536

Kloot (developer)

2018-11-13 13:20

 At the moment the only way is to run Spring inside a debugger. On Windows this requires installing the MinGW version of gdb and downloading / extracting the debug symbols for 889-g0871f35 from https://springrts.com/dl/buildbot/default/maintenance/104.0.1-889-g0871f35/win32/%7bmaintenance%7d104.0.1-889-g0871f35_win32_spring_dbg.7z alongside the executable.

I can also hack the engine in a special branch but that will take longer.

~0019537

Google_Frog (reporter)

2018-11-13 13:24

 I dug up another. 104.0.1-483-g30d8543 has the bug: https://github.com/ZeroK-RTS/CrashReports/issues/16734

~0019541

Kloot (developer)

2018-11-13 20:27

Last edited: 2018-11-13 20:51

View 2 revisions

 https://springrts.com/dl/buildbot/default/mantis6077/104.0.1-891-ga7863eeeba/win64/

run this, then attach the generated mantis6077.txt which should contain a trace.

~0019542

Google_Frog (reporter)

2018-11-14 02:14

 I don't usually run the 64 bit builds, so I will also run the 32 bit one. Here is the 64 bit crash: https://github.com/ZeroK-RTS/CrashReports/issues/16763

~0019543

Google_Frog (reporter)

2018-11-14 02:16

 Here is 32 bit. https://github.com/ZeroK-RTS/CrashReports/issues/16764

Ignore the title of the crash reports, I'm replacing an engine locally instead of uploading it to zk infrastructure and downloading it with the wrapper.

~0019544

Kloot (developer)

2018-11-14 12:29

Last edited: 2018-11-14 12:33

View 3 revisions

 thanks, https://springrts.com/dl/buildbot/default/mantis6077/104.0.1-892-g94e95c4/win32/ should exit cleanly again. merge into maintenance is pending confirmation.

~0019545

Google_Frog (reporter)

2018-11-14 13:00

 I just tested and the issue seems to be resolved.

~0019546

Kloot (developer)

2018-11-14 18:39

 Fix f17149dfdfd0c85f8ae86450edfea50e52df023f committed to develop branch: fix 0006077 redux, repo: spring changeset id: 11134

~0019547

Kloot (developer)

2018-11-14 18:40

 Fix fbcf84a3fefca290e59cbde451fb040f3aa1f149 committed to maintenance branch: fix 0006077 redux, repo: spring changeset id: 11135
+Notes

-Issue History
Date Modified Username Field Change
2018-11-12 05:49 Google_Frog New Issue
2018-11-12 08:24 Google_Frog Note Added: 0019522
2018-11-12 10:57 abma Note Added: 0019523
2018-11-12 10:58 abma Summary 104.0.1-888-g15d6cc6 maintenance Every closure of Spring results in a crash exit code => 104.0.1-888-g15d6cc6 maintenance crash at exit with -107374181 / 0xC0000005L / STATUS_ACCESS_VIOLATION
2018-11-12 10:59 abma Severity minor => crash
2018-11-12 13:10 Google_Frog Note Added: 0019524
2018-11-12 13:11 Google_Frog Note Added: 0019525
2018-11-12 13:12 abma Note Added: 0019526
2018-11-12 13:24 Changeset attached => spring develop 4ed0b9e1
2018-11-12 13:24 Anonymous Note Added: 0019527
2018-11-12 13:24 Changeset attached => spring maintenance 0871f35d
2018-11-12 13:24 Anonymous Note Added: 0019528
2018-11-12 13:35 Kloot Assigned To => Kloot
2018-11-12 13:35 Kloot Status new => resolved
2018-11-12 13:35 Kloot Resolution open => fixed
2018-11-12 13:35 Kloot Fixed in Version => 104.0 +git
2018-11-12 13:35 Kloot Note Added: 0019529
2018-11-13 03:15 Google_Frog Status resolved => feedback
2018-11-13 03:15 Google_Frog Resolution fixed => reopened
2018-11-13 03:15 Google_Frog Note Added: 0019532
2018-11-13 11:09 Kloot Note Added: 0019533
2018-11-13 12:46 Google_Frog Note Added: 0019534
2018-11-13 12:46 Google_Frog Status feedback => assigned
2018-11-13 13:09 Google_Frog Note Added: 0019535
2018-11-13 13:20 Kloot Note Added: 0019536
2018-11-13 13:24 Google_Frog Note Added: 0019537
2018-11-13 20:27 Kloot Note Added: 0019541
2018-11-13 20:51 Kloot Note Edited: 0019541 View Revisions
2018-11-14 02:14 Google_Frog File Added: mantis6077_64.txt
2018-11-14 02:14 Google_Frog Note Added: 0019542
2018-11-14 02:16 Google_Frog File Added: mantis6077_32.txt
2018-11-14 02:16 Google_Frog Note Added: 0019543
2018-11-14 12:29 Kloot Note Added: 0019544
2018-11-14 12:33 Kloot Note Edited: 0019544 View Revisions
2018-11-14 12:33 Kloot Note Edited: 0019544 View Revisions
2018-11-14 12:34 Kloot Status assigned => feedback
2018-11-14 13:00 Google_Frog Note Added: 0019545
2018-11-14 13:00 Google_Frog Status feedback => assigned
2018-11-14 18:39 Kloot Changeset attached => spring develop f17149df
2018-11-14 18:39 Kloot Note Added: 0019546
2018-11-14 18:39 Kloot Status assigned => resolved
2018-11-14 18:39 Kloot Resolution reopened => fixed
2018-11-14 18:40 Kloot Changeset attached => spring maintenance fbcf84a3
2018-11-14 18:40 Kloot Note Added: 0019547
2020-07-08 20:08 abma Relationship added related to 0006398
+Issue History