You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After starting a new game and attempting to watch the intro video, a memory leak occurs, causing the computer to freeze. It’s worth noting that this only happens when the "log type" is set to sync—when it's set to async, the issue does not occur. Another important point is that switching from async to sync prevents further memory leaks from appearing (after restarting PC, the issue returned). It can also be added that even if you have async enabled there is a very high consumption of ram for a while
Reproduction Steps
Set log type to sync.
Specify OS Version
Windows 11
CPU
i7-13700k
GPU
RTX 4080
Amount of RAM in GB
32 GB
Amount of VRAM in GB
16 GB
Log File
Sync: Kilsync.txt
Async: Kilasync.txt (The error Shader binary info not found. appears after the end of the introductory video)
Async -> sync: Kilassyn.txt Same results as in async (I think so)
The text was updated successfully, but these errors were encountered:
Resogun also has a problem with sync log type. When log type is set to sync game doesn't boot to menu (and crashes without any errors) but when log type is set to async game boots to menu
Graubek
changed the title
[GAME BUG]: CUSA00002 - KILLZONE™ SHADOW FALL (memory leak)
[GAME BUG]: CUSA00002 - KILLZONE™ SHADOW FALL (memory leak and problem with "log type")
May 15, 2025
Just to be clear: the difference between async and sync logging is usually performance, what you’re really seeing here is likely timing related issues.
Uh oh!
There was an error while loading. Please reload this page.
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
After starting a new game and attempting to watch the intro video, a memory leak occurs, causing the computer to freeze. It’s worth noting that this only happens when the "log type" is set to sync—when it's set to async, the issue does not occur. Another important point is that switching from async to sync prevents further memory leaks from appearing (after restarting PC, the issue returned). It can also be added that even if you have async enabled there is a very high consumption of ram for a while
Reproduction Steps
Set log type to sync.
Specify OS Version
Windows 11
CPU
i7-13700k
GPU
RTX 4080
Amount of RAM in GB
32 GB
Amount of VRAM in GB
16 GB
Log File
Sync: Kilsync.txt
Async: Kilasync.txt (The error
Shader binary info not found
. appears after the end of the introductory video)Async -> sync: Kilassyn.txt Same results as in async (I think so)
The text was updated successfully, but these errors were encountered: