DCS World multiplayer crash and memory leak problem

[Irisz]

I just wanted to fly my favorite Flanker and DCS World crashed!

Here are the log files, I already sent the log files to the ED server when DCS World crashed, but I will send them here too!

49,213 MB of my physical memory was used after 7 minutes of online playing! Low texture setting and the map texture is also set to Low.

Thanks!

dcs.log-20240915-061413.zip

Here is the gameplay and the crash!

Edited September 15, 2024 by Irisz

[sleighzy]

Drop your zip file in the #dcs-log-analyzer channel in the DCS discord, https://discord.com/channels/542985647502393346/1179171301651402802 and it will provide some advice. I dropped it in there for you (but you’ll need to do yourself as well as it only last 5 mins) but it highlighted a potential crash with a RAM memory timing issue and to remove overclocking XMP on the RAM. There were a few other options for troubleshooting as well. 

[Irisz]

45 minutes ago, sleighzy said:

Drop your zip file in the #dcs-log-analyzer channel in the DCS discord, https://discord.com/channels/542985647502393346/1179171301651402802 and it will provide some advice. I dropped it in there for you (but you’ll need to do yourself as well as it only last 5 mins) but it highlighted a potential crash with a RAM memory timing issue and to remove overclocking XMP on the RAM. There were a few other options for troubleshooting as well. 

Thank you very much! My memory is on CL 14, that's all I did tuning, nothing else. I'll take it down to default XMP!

Edited September 15, 2024 by Irisz

[Irisz]

Errors
Your DCS has crashed
The crash occurred inside edCore.dll.

(edCore):
LinkHost::ResetLinks + 0x17
(edObjects):
viMovingObject::~viMovingObject + 0x36
(WorldGeneral):
woLABase::~woLABase + 0x12
(DCS):
SW + 0x6F345
(DCS):
SW + 0x381E15
[...]

fxo and metashaders2 folders delete.

Complete file system repair in progress.

Full repair found no errors.

• LinkHost::ResetLinks + 0x17

  • This likely refers to a function called ResetLinks within a class or module named LinkHost. The + 0x17 indicates an offset within the function where an issue occurred. In technical terms, the program crashed or reset at this specific point in memory.

• (edObjects): viMovingObject::~viMovingObject + 0x36

  • The viMovingObject::~viMovingObject is a destructor for a class called viMovingObject, possibly representing a moving object in the simulation or game world. The ~ symbol indicates it's a destructor, meaning it's cleaning up or deleting an object. The + 0x36 shows the memory offset where the issue happened.

• (WorldGeneral): woLABase::~woLABase + 0x12

  • Similar to the previous line, this refers to the destructor of an object called woLABase within a module or namespace called WorldGeneral. This is where the program was handling the deletion of an object, and an issue arose at offset 0x12.

• (DCS): SW + 0x6F345

  • This line likely refers to some internal function or module within the DCS simulation, and SW might be a specific function, subroutine, or process. The + 0x6F345 is the memory address where the issue occurred.

• (DCS): SW + 0x381E15

  • Similarly to the previous line, this points to another instance within DCS where a problem happened, this time at offset 0x381E15.

 

No story, I set my memory to default XMP and don't tuning anymore!

There is XMP default, we hope there will be no more crashes!

Edited September 15, 2024 by Irisz

[Irisz]

Thank you Sir, glory to you, we hope there are no more crashes, my memory is running on XMP default and I streamed a good one, with 4 kills and 1 takeoff in my favorite Flanker!