View Issue Details

IDProjectCategoryView StatusLast Update
0002808Spring engineGeneralpublic2011-12-04 16:51
ReporterGoogle_Frog Assigned Tozerver  
PrioritynormalSeveritycrashReproducibilitysometimes
Status resolvedResolutionfixed 
Product Version84.0 
Fixed in Version85.0 
Summary0002808: C++ runtime error
DescriptionSometimes spring crashes at startup with a 'C++ runtime error'. After an error the game can usually be rejoined successfully. From my observation it happens to many people and at least one person crashes at startup in about half the games I have seen.
TagsNo tags attached.
Attached Files
infolog_runtime2.txt (Attachment missing)
infolog_runtime.txt (Attachment missing)
Checked infolog.txt for Errors

Relationships

duplicate of 0002804 resolvedKloot Mid Game Crash in ZK 
duplicate of 0002758 resolvedzerver Hang during pathing 

Activities

Google_Frog

2011-12-04 08:09

reporter   ~0007815

runtime2 infolog. Another crash.

Playing normally then:

Microsoft Visual C++ Runtime Library
Runtime Error!
This application has requested Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

Click OK:

Spring.exe - Application Error
The instruction at "0x6b623ee6" referenced memory at "0x019cb968". The memory could not be "read".
Click on OK to terminate the program.

Google_Frog

2011-12-04 08:11

reporter   ~0007816

Oops, forgot to upload first infolog. Crash at startup is "infolog_runtime.txt".

Google_Frog

2011-12-04 08:15

reporter   ~0007817

Like the first crash, second does not occur on rejoin.

hoijui

2011-12-04 12:43

reporter   ~0007819

could this also be LoadMT related?
could you check if LoadMT=0 in spring settings makes it go away?

Google_Frog

2011-12-04 13:06

reporter   ~0007822

With difficulty. I have had the loading crash once myself so I wouldn't be sure and it is hard to collect data. Our best bet would be to set LoadMT=0 for everyone and check if it goes away.

zerver

2011-12-04 16:51

reporter   ~0007824

The infologs you provided are two separate bugs, both have been resolved.

Issue History

Date Modified Username Field Change
2011-12-04 06:08 Google_Frog New Issue
2011-12-04 08:09 Google_Frog Note Added: 0007815
2011-12-04 08:10 Google_Frog File Added: infolog_runtime2.txt
2011-12-04 08:10 Google_Frog File Added: infolog_runtime.txt
2011-12-04 08:11 Google_Frog Note Added: 0007816
2011-12-04 08:15 Google_Frog Note Added: 0007817
2011-12-04 12:43 hoijui Note Added: 0007819
2011-12-04 13:06 Google_Frog Note Added: 0007822
2011-12-04 16:49 zerver Relationship added duplicate of 0002804
2011-12-04 16:50 zerver Relationship added duplicate of 0002758
2011-12-04 16:51 zerver Note Added: 0007824
2011-12-04 16:51 zerver Status new => resolved
2011-12-04 16:51 zerver Fixed in Version => 85.0
2011-12-04 16:51 zerver Resolution open => fixed
2011-12-04 16:51 zerver Assigned To => zerver