[Bug]: Memory crash with this mod activated.

[MultiKoopa]

Describe the bug

Windows 11 64-bit, GTX 1070, i5-10400f, 16 GB RAM
Yuzu v1734
Set TOTK Optimizer to Switch graphics preset, changed resolution to 1080p

Was working fine throughout the tutorial island. Now, every 10-15 minutes or so, Yuzu will completely freeze; the log shows this line repeating forever:

[1485.697101] HW.Memory <Error> core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008

Reproduction steps

Random; no idea what triggers it.

Additional context

No response

What's your operating system?

Windows 11

[MaxLastBreath]

this in particular isn't very helpful 0x0000000000000008 however if u can trigger a crash on ryujinx or switch it'll be more helpful to figure out what the issue is

[MultiKoopa]

this in particular isn't very helpful 0x0000000000000008 however if u can trigger a crash on ryujinx or switch it'll be more helpful to figure out what the issue is

I went thousands of lines deeper, and found this just before the thousands of lines of 0x0000000000000000008 stuff:

[1475.936419] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000038 [1475.936443] HW.Memory core\memory.cpp:operator ():741: Unmapped Read8 @ 0x0000000000000080 [1475.936448] HW.Memory core\memory.cpp:operator ():741: Unmapped Read8 @ 0x0000000000000081 [1475.936453] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000030 [1475.936457] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000034 [1475.936461] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000038 [1475.936465] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000040 [1475.936472] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000050 [1475.936681] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000028 [1475.936690] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000068 [1475.936695] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000010 [1475.936699] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000028 [1475.936703] HW.Memory core\memory.cpp:operator ():741: Unmapped Read16 @ 0x0000000000000078 [1475.936707] HW.Memory core\memory.cpp:operator ():741: Unmapped Read16 @ 0x000000000000007A [1475.936711] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x000000000000007C [1475.936717] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000000 [1475.936749] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008 [1475.936834] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000000000000000 [1475.936842] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000000000000000 [1475.936846] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000028 [1475.936857] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000010 [1475.936863] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000002128D912F8 [1475.936868] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000002128DB9770 [1475.936872] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000000 [1475.936876] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008 [1475.936882] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000002128DB9B60 [1475.936886] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000002128D912F8

[MaxLastBreath]

this in particular isn't very helpful 0x0000000000000008 however if u can trigger a crash on ryujinx or switch it'll be more helpful to figure out what the issue is

I went thousands of lines deeper, and found this just before the thousands of lines of 0x0000000000000000008 stuff:

[1475.936419] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000038 [1475.936443] HW.Memory core\memory.cpp:operator ():741: Unmapped Read8 @ 0x0000000000000080 [1475.936448] HW.Memory core\memory.cpp:operator ():741: Unmapped Read8 @ 0x0000000000000081 [1475.936453] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000030 [1475.936457] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000034 [1475.936461] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000038 [1475.936465] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000040 [1475.936472] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000050 [1475.936681] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000028 [1475.936690] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000068 [1475.936695] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000010 [1475.936699] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000028 [1475.936703] HW.Memory core\memory.cpp:operator ():741: Unmapped Read16 @ 0x0000000000000078 [1475.936707] HW.Memory core\memory.cpp:operator ():741: Unmapped Read16 @ 0x000000000000007A [1475.936711] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x000000000000007C [1475.936717] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000000 [1475.936749] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008 [1475.936834] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000000000000000 [1475.936842] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000000000000000 [1475.936846] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000028 [1475.936857] HW.Memory core\memory.cpp:operator ():741: Unmapped Read32 @ 0x0000000000000010 [1475.936863] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000002128D912F8 [1475.936868] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000002128DB9770 [1475.936872] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000000 [1475.936876] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008 [1475.936882] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000000 = 0x0000002128DB9B60 [1475.936886] HW.Memory core\memory.cpp:operator ():765: Unmapped Write64 @ 0x0000000000000008 = 0x0000002128D912F8

Yeah those don't really mean anything, it could be thousands of things causing unmapped memory read unrelated to the mod, could just be yuzu or your dump too.

[MultiKoopa]

Gotcha. Appreciate the responses :)

[MultiKoopa]

I redid the mod, but chose 720p instead of 1080p this time.

Haven't had a crash in many hours.

Maybe my system just can't handle 1080p internal resolution?

Doesn't explain the problem fully, but it's gone for now.

[prototype619]

Assume he's referring to the same problem I'm having. I'm unable to use this mod otherwise these crashes happen at random. Could be an hour in could be 5 min in

If there is a specific place to obtain a log please let me know and I'll go get it.

I can certainly say it's only with this mod enabled.

The main Ryujinx log folder has no mention of the crash it just dies and can only see this on event viewer.

Win 11 3080ti Ryzen 5 7600x I should be fine with the 1080p preset and it crashes.

[MaxLastBreath]

I redid the mod, but chose 720p instead of 1080p this time.

Haven't had a crash in many hours.

Maybe my system just can't handle 1080p internal resolution?

Doesn't explain the problem fully, but it's gone for now.

could you try enabling the memory setting in Ryujinx, it's under system, under Hacks.

[MultiKoopa]

I redid the mod, but chose 720p instead of 1080p this time. Haven't had a crash in many hours. Maybe my system just can't handle 1080p internal resolution? Doesn't explain the problem fully, but it's gone for now.

could you try enabling the memory setting in Ryujinx, it's under system, under Hacks.

I'm on Yuzu. The game is practically unplayable on ryujinx for me even with optimizer; constantly goes below 20 fps

[MaxLastBreath]

Assume he's referring to the same problem I'm having. I'm unable to use this mod otherwise these crashes happen at random. Could be an hour in could be 5 min in

If there is a specific place to obtain a log please let me know and I'll go get it.

I can certainly say it's only with this mod enabled.

The main Ryujinx log folder has no mention of the crash it just dies and can only see this on event viewer.

Win 11 3080ti Ryzen 5 7600x I should be fine with the 1080p preset and it crashes.

If you find a way to consistently trigger a crash it would be extremely useful for debugging. If it crashes randomly it could be quite a lot of things going wrong. Usually when a mod crashes there should be a PC/LR log with Memory addresses showing the "Crash Site" of the crash. As that would mean something was NULL and it was being read or something was just not working correctly with the mod itself. Therefore Ryujinx crashlog would be the place to look for more information on what's going on, for me, this current version has not crashed once in like 3 hours benchmark on Ryujinx, Given i was using 4k with 4K shadows though, or rather the HIGH preset. RTX 3080, R7 5800x3d, 32gb DRAM. PS you can also revert to the old version of the Optimizer simply by downloading UltraCam from https://gamebanana.com/mods/480138 Version 2.1 and changing the subsdk3 in !!!TOTKOptimizer/exefs folder to the old one from gamebanana.

[Louk997]

Got the exact same issue. I played the game without issues for 30 hours, now the game randomly crashes every 5-15 min.

[ 312.544292] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000018 [ 312.544298] HW.Memory core\memory.cpp:operator ():741: Unmapped Read64 @ 0x0000000000000008

I don't know if it's linked to the mod, I found this thread while searching for a solution.

It's weird that we got the same exact issue. Already tried to delete the shaders but to no avail.

[JuanPabloPearce]

I think this and #163 are related as both are memory crashes.