I’m working on a big project using UE4 (stellar overload), and I’m just wondering why the Visual Studio’s output is spammed by thread exit message while the project is running. For example:
The thread 0x63ac has exited with code 1 (0x1).
The thread 0x3cf4 has exited with code 1 (0x1).
The thread 0x47ac has exited with code 1 (0x1).
The thread 0x5640 has exited with code 1 (0x1).
The thread 0x87a0 has exited with code 1 (0x1).
The thread 0x7d48 has exited with code 1 (0x1).
The thread 0x5940 has exited with code 1 (0x1).
Each log come by packets: exactly 4 messages each 2/3 seconds.
This spam occurs during game play, but also in the editor itself (before launching the game).
I tried to randomly to pause the execution, but I’m not able to define precisely what is going on. I suspect the “compile shader” thread, but not sure at all.
Check out Process Monitor from Sysinternals. This tool is capable of monitoring all thread creation and exiting while you are debugging.
Process Monitor can give you the stack and used modules, which could help you finding your problem about identifying your threads.
So, using Process Monitor, it appears that these Threads are spammed by msvsmon.exe, witch is the remote debugger of visual studio.
So I don’t know, maybe it’s a normal behaviour?
When I debug my project, I do not get any threads exiting with errors and no spamming from the remote debugger (only at closing around 15 exiting threads). And the threads showed in the output of VS are from “UE4Editor.exe” (sub from remote debugger) not from the debugger itself. Here a little screeny (filtered UE4Editor.exe):
