Author Topic: Hard lock while loading a race - possible memory leak  (Read 74 times)

gaspump

  • Posts: 2
Was just playing for my first time (having a ton of fun!) and after about three hours I had a hard lock while loading a race.  A number of related things were logged in the Windows Event logs.  I did a forum search and didn't find a match.  Figured I'd report it just in case.

First event, 9:14:32pm:
Faulting application name: crashpad_handler_64.exe, version: 0.0.0.0, time stamp: 0x59038c68
Faulting module name: crashpad_handler_64.exe, version: 0.0.0.0, time stamp: 0x59038c68
Exception code: 0xc0000409
Fault offset: 0x0000000000130cc1
Faulting process id: 0x4cf4
Faulting application start time: 0x01d4004415d1bcb0
Faulting application path: S:\Steam\steamapps\common\Bugbear Entertainment\crash\crashpad_handler_64.exe
Faulting module path: S:\Steam\steamapps\common\Bugbear Entertainment\crash\crashpad_handler_64.exe
Report Id: 25f8230e-d900-452e-a9f6-759f028ded2f
Faulting package full name:
Faulting package-relative application ID:

The exception code is for a buffer overrun event.  Smells like memory leak.

WER kicked in a couple of events of no note about it doing it's solutions checks which I actually couldn't see.  Primary display was very wonky while this was happening with the load screen staying on top of everything else.  Then the window manager crashed a minute later at 9:15:49

Faulting application name: dwm.exe, version: 10.0.16299.15, time stamp: 0x7f22d77c
Faulting module name: dwmcore.dll, version: 10.0.16299.402, time stamp: 0x20621821
Exception code: 0xc00001ad
Fault offset: 0x000000000019425a
Faulting process id: 0x4f8
Faulting application start time: 0x01d3e73a6dac16eb
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\dwmcore.dll
Report Id: 71da7b0f-d96a-4633-8538-fd08b7de2bb3
Faulting package full name:
Faulting package-relative application ID:

Hard to find info about that exception code but results suggest an out of memory condition.  Further suspicion about a slow memory leak leading to resource exhaustion and then the crash event.

Not sure I can reproduce, but I can set up WER to catch a crash dump in case it happens again if you think there'd be some value in it.

PC specs are definitely not in the toaster range:
Win 10 Home 64bit
Intel i7 8800
16GB Corsair DDR4 RAM
MSI GTX1080ti Gaming w/ 11GB VRAM
MSI Z370 Gaming Pro Carbon mobo
ROG PG279Q monitor, 2560x1440@150Hz

Edit: Corrected motherboard model number.  Oops!
« Last Edit: June 10, 2018, 09:22:09 AM by gaspump »

The Very End

  • *
  • *
  • Posts: 2263
That's a great report! Lot of details. I am sure BB will look at it and try to analyse it.

gaspump

  • Posts: 2
Thanks!  I work in software support myself so I have a pretty good idea of where to at least start looking for clues, and I know how important it is to have accurate and detailed information.  The more information the better!  I've enabled full memory dumps via WER so if it does happen again I will report back and link to the dump.  Without dev's symbols I won't be able to tell much on my own.