Help identify memory issue in CTD?

[reffegy]

Attached is the crash log crash-2024-10-21-06-14-15.log. I'm not certain what went wrong and when, but I cannot get more than three to four seconds into a save without experiencing a CTD. I'm not incredibly savvy with reading crash logs, but I'm going to assume there is a memory leak somewhere.

 

Also, if there are any other obvious fuck-ups IRT mod conflicts and such, please point them out. Thanks!

[traison]

It crashed because it tried to dereference RAX which was 0x0. This is a null pointer.

 

The issue is most likely in form id 0x0004D6ED (DOOR) reference id 0x0002A504, in form id 0x00016BD7 "Temple of Mara", modified by Lux.esp.

 

4 hours ago, reffegy said:

I'm not incredibly savvy with reading crash logs, but I'm going to assume there is a memory leak somewhere.

 

Memory leaks look different:

1. Since you said this crashes within seconds, that would mean all your RAM and your swap file filled up in seconds. While not impossible, that's quite unlikely. This would start as extreme stuttering, as the swap file is several times slower than your RAM, even if it was on a fast M.2 drive.
2. The more likely memory leak is one that becomes a problem after a long time: a few hours in, or after a week of continuous execution of a program. Typically leaks are small, a couple of bytes here, a couple of bytes there. Anything more substantial would show up in profiling applications that any serious developer should be using.

[reffegy]

Thank you for your quick reply :^)

 

Gotta be honest, I'm kind of at a loss as to how I should diagnose and handle this issue. Is the crux of it simply Lux?

 

I saw the repeated references to Lux and the Temple of Mara in the first few lines of the crash log—and I found zero forum posts pertaining to issues between the two.

[traison]

1 hour ago, reffegy said:

I'm kind of at a loss as to how I should diagnose and handle this issue.

 

What I'd do is load everything as-is in xEdit and inspect the records involved in there. Resolve conflicts and keep an eye out for missing record fields, especially fields that used to be defined but no longer are because of some mod. If that doesn't help then probably a closer inspection of the crash log is needed.