PDA

View Full Version : crashing to desktop since version 4.9.1.6 update



Smoky McAshtray
02-14-2018, 01:47 AM
Since version 4.9.1.6 I have been experiencing frequent crashes to desktop. I've had random intermittent crashes before that just hid in the background and the app would stop running. No big deal there as it didn't interfere with the sim. Now with the latest updates, I'm getting frequent and regular crashes to desktop that will pull iRacing off of full screen (3 monitor Nvidia Surround). Needless to say, this is not something I can work around, and I'm now having to forego using Crew Chief and back to the default spotter. I was hoping the 4.9.1.7 update would fix it, but the crashes are still present. Any idea what could be causing this? I'd love to have my crew chief back as I find it an invaluable tool. Thanks so much for the great product.

Sparten
02-14-2018, 06:22 AM
I think your having the same problem as reported in this thread http://thecrewchief.org/showthread.php?374-error-report, so if you can please also post the error from windows event viewer it would be helpful.

Nintastio
02-15-2018, 06:41 PM
I am having this same issue. The guy in the other thread seems to be having issues with crashing during session transitions but like Smoky here I am having issues with the game crashing right in the middle of a race. This app seems great, but every time I try to use it, it ends by minimizing my game to display the app crash notification and of course me running off the course or into another car.

Nintastio
02-15-2018, 07:00 PM
Here are the error logs if they will help determine the issue

*First Error*
Error 2/14/2018 7:17:11 PM .NET Runtime 1026 None

Log Name: Application
Source: .NET Runtime
Date: 2/14/2018 7:17:11 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: 8700k.nintastio
Description:
Application: CrewChiefV4.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at System.Buffer.Memmove(Byte*, Byte*, UInt64)
at System.String.CtorCharPtrStartLength(Char*, Int32, Int32)
at iRSDKSharp.YamlParser.Parse(System.String, System.String)
at CrewChiefV4.iRacing.Driver.ParseDynamicSessionInfo (System.String)
at CrewChiefV4.iRacing.Sim.GetDrivers(System.String, Boolean)
at CrewChiefV4.iRacing.Sim.SdkOnSessionInfoUpdated(Sy stem.String, Int32, Int32)
at CrewChiefV4.iRacing.iRacingSharedMemoryReader.Read GameData(Boolean)
at CrewChiefV4.CrewChief.Run(System.String, Boolean)
at CrewChiefV4.MainWindow.runApp()
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


Event Xml:
<Event xmlns="schemas.microsoft/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-15T01:17:11.530207900Z" />
<EventRecordID>1154488</EventRecordID>
<Channel>Application</Channel>
<Computer>8700k.nintastio.com</Computer>
<Security />
</System>
<EventData>
<Data>Application: CrewChiefV4.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at System.Buffer.Memmove(Byte*, Byte*, UInt64)
at System.String.CtorCharPtrStartLength(Char*, Int32, Int32)
at iRSDKSharp.YamlParser.Parse(System.String, System.String)
at CrewChiefV4.iRacing.Driver.ParseDynamicSessionInfo (System.String)
at CrewChiefV4.iRacing.Sim.GetDrivers(System.String, Boolean)
at CrewChiefV4.iRacing.Sim.SdkOnSessionInfoUpdated(Sy stem.String, Int32, Int32)
at CrewChiefV4.iRacing.iRacingSharedMemoryReader.Read GameData(Boolean)
at CrewChiefV4.CrewChief.Run(System.String, Boolean)
at CrewChiefV4.MainWindow.runApp()
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

</Data>
</EventData>
</Event>

*Second Error*
Error 2/14/2018 7:17:11 PM Application Error 1000 (100)

Log Name: Application
Source: Application Error
Date: 2/14/2018 7:17:11 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: 8700k.nintastio
Description:
Faulting application name: CrewChiefV4.exe, version: 1.0.0.0, time stamp: 0x5a82cda8
Faulting module name: mscorlib.ni.dll, version: 4.7.2633.0, time stamp: 0x5a4ed653
Exception code: 0xc0000005
Fault offset: 0x00000000004c8bf4
Faulting process id: 0x388c
Faulting application start time: 0x01d3a5e6d7ce11e2
Faulting application path: C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe
Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\msc orlib\a39512bde949dc065175a3be81664375\mscorlib.ni .dll
Report Id: 2fff8de6-02eb-4a61-a129-a086969e1f8c
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-15T01:17:11.836022200Z" />
<EventRecordID>1154489</EventRecordID>
<Channel>Application</Channel>
<Computer>8700k.nintastio.com</Computer>
<Security />
</System>
<EventData>
<Data>CrewChiefV4.exe</Data>
<Data>1.0.0.0</Data>
<Data>5a82cda8</Data>
<Data>mscorlib.ni.dll</Data>
<Data>4.7.2633.0</Data>
<Data>5a4ed653</Data>
<Data>c0000005</Data>
<Data>00000000004c8bf4</Data>
<Data>388c</Data>
<Data>01d3a5e6d7ce11e2</Data>
<Data>C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe</Data>
<Data>C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\msc orlib\a39512bde949dc065175a3be81664375\mscorlib.ni .dll</Data>
<Data>2fff8de6-02eb-4a61-a129-a086969e1f8c</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

mr_belowski
02-15-2018, 07:15 PM
Thanks for the log. The errors are all in the same place in the code. The iracing SDK includes 2 different parsers to process session data. The default one is painfully slow (like, 1 second to process the data every time a session changed or leaderboard positions change). The alternate one takes only a few milliseconds to process the same data but, as we've found out crashes. To make matters worse these crashes don't happen when running in debug mode.

We've got a version of the app in testing now which has some additional checks in this parser code to (hopefully) prevent these memory errors but they're very hard to reproduce. Expect an update tomorrow

Nintastio
02-15-2018, 08:45 PM
Awesome, thanks for the quick response! Since the crash originates from the same part of the code I will continue to follow the other thread you posted above. I can also do some software testing if you need more test subjects.

The Iron Wolf
02-15-2018, 09:26 PM
We frequently have Betas. If we could get more feedback (testing) from those, it would greatly help improving CC quality :)

A bit of resources if you'd like to contribute:
Beta thread: http://thecrewchief.org/showthread.php?38-Beta-Test-Thread
Our Discord channel: http://thecrewchief.org/showthread.php?492-Crew-Chief-Discord-server
For logic errors (not crashes like this issue, as it is too late) it really helps if they are reported via trace: http://thecrewchief.org/showthread.php?142-How-to-collect-Crew-Chief-repro-traces

We've made trace collection much less demanding in terms of disk space (in the upcoming version). One of the better ways to help improving support of any game in CC is to play with trace collection enabled and report weirdnesses with a trace :)