Results 1 to 6 of 6

Thread: crashing to desktop since version 4.9.1.6 update

  1. #1

    crashing to desktop since version 4.9.1.6 update

    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.

  2. #2
    VP PR Manager Sparten's Avatar
    Join Date
    Feb 2017
    Posts
    357
    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.

  3. #3
    Junior Member
    Join Date
    Feb 2018
    Posts
    2
    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.

  4. #4
    Crew Chief Mega Corp CEO mr_belowski's Avatar
    Join Date
    Feb 2017
    Posts
    946
    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

  5. #5
    Junior Member
    Join Date
    Feb 2018
    Posts
    2
    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.

  6. #6
    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.p...ta-Test-Thread
    Our Discord channel: http://thecrewchief.org/showthread.p...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.p...f-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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •