(Possible) Memory leaks resulting in client crashes
[No workaround or official answer regarding this issue so far]
I've been recently following some issues regarding to game crashes.
These issues had users having their client crash responding with an error indicating that the client was trying to allocate terabytes of memory.
(This is an indication of a memory leak)
Now clients are crashing without producing this error directly, possibly in some instances freezing the entire computer due to said issue.
We've received some .dmp files from users encountering this error, I've attatched them to this post.
After analyzing these files, it seems like the application is attempting to write or read an invalid memory address.
With recent issues related to memory leaks, I assumed that this would most likely be related to that.
This is something that cannot be resolved on the user's side, so it's definitely an issue related to the code.
Here is an Analyzed .dmp file:
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Execute
Key : Analysis.CPU.mSec
Value: 812
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 816
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 16587
Key : Analysis.Memory.CommitPeak.Mb
Value: 97
Key : Timeline.Process.Start.DeltaSec
Value: 1142
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
Key : WER.Process.Version
Value: 9.18.944.0
FILE_IN_CAB: ee3ceba1-638e-471d-a04e-ba3729293e12.dmp
CONTEXT: (.ecxr)
rax=0000000014800000 rbx=0000000000000009 rcx=0000000000000033
rdx=0000000000000f6d rsi=0000000000000033 rdi=000001fd86f4fc30
rip=00007ff73104a73c rsp=000000a629f9c850 rbp=000000a629f9e710
r8=000001fec67bedc0 r9=000000a629f9ca28 r10=0000000000001480
r11=0000000000000000 r12=0000000000000001 r13=000001fd8701f830
r14=0000000000000033 r15=000001fd86f2fae8
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
r5apex+0x21a73c:
00007ff7`3104a73c f0ff0529b0de01 lock inc dword ptr [r5apex+0x200576c (00007ff7`32e3576c)] ds:00007ff7`32e3576c=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff73104a73c (r5apex+0x000000000021a73c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 00007ff7f595463c
Attempt to execute non-executable address 00007ff7f595463c
PROCESS_NAME: r5apex.exe
EXECUTE_ADDRESS: 7ff7f595463c
FAILED_INSTRUCTION_ADDRESS:
r5apex+21a73c
00007ff7`3104a73c f0ff0529b0de01 lock inc dword ptr [r5apex+0x200576c (00007ff7`32e3576c)]
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 00007ff7f595463c
IP_ON_HEAP: 000001fe41b60a40
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.
FRAME_ONE_INVALID: 1
STACK_TEXT:
000000a6`29f9c850 000001fe`41b60a40 : 000001fd`8701f830 ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 : r5apex+0x21a73c
000000a6`29f9c858 000001fd`8701f830 : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 000001fe`41b60b30 : 0x000001fe`41b60a40
000000a6`29f9c860 ffffffff`ffffffff : ffffffff`ffffffff 00000000`00000000 000001fe`41b60b30 000001fe`41b60b60 : 0x000001fd`8701f830
000000a6`29f9c868 ffffffff`ffffffff : 00000000`00000000 000001fe`41b60b30 000001fe`41b60b60 00000000`00000000 : 0xffffffff`ffffffff
000000a6`29f9c870 00000000`00000000 : 000001fe`41b60b30 000001fe`41b60b60 00000000`00000000 00000000`4c979688 : 0xffffffff`ffffffff
SYMBOL_NAME: r5apex+21a73c
MODULE_NAME: r5apex
IMAGE_NAME: r5apex.exe
STACK_COMMAND: ~11s; .ecxr ; kb
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_r5apex.exe!Unknown
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.0.0
FAILURE_ID_HASH: {97ecc5bf-25a5-a91f-408d-00e3953f49af}
Followup: MachineOwner
---------
