Hello,
we’re using unreal 5.5.2. As we try to inspect memory using Unreal Insight, starting the game with the parameters -trace=default,memory makes the game crash during the intialization phase.
If we remove the “memory” parameter we don’t have the crash.
[Image Removed]\
I see on Perforce (Main branch) that there are recent changes on the scheduler/task/threads files that seem related to the callstack we’re seeing so I took their latest versions and their dependencies until the project compiles. Even with these changes, the crash happens.
Any help or advice would be very appreciated,
thank you !
Looks like a recursive issue (there is 70 hidden frames on “Background worker #0”) related to the Oversubscription scope. I haven’t seen it here, and we test with “default,memory” channels all the time. Could you try disabling the “default” channel as see if you can run memory tracing? Or alternatively since “default” is preset you can manually expand it and exclude the “cpu” channel.
I’m also a bit surprised to see FWindowsPlatformStackWalk, are you guys compiling with Clang on Windows?
In general you should know that detailed memory profiling brings quite a lot of overhead (mainly due to stack unwinding), so performance numbers are likely too skewed to be useful.