I recently switched to UE5 and I find that I experience freezes whenever I hit a breakpoint, which as you can imagine makes debugging very tedious.
I really don’t know what happens and I’m positive I did not have that in UE4. The engine gets completely stuck and the only way out is to kill it via Ctrl+Alt+Del, where it is listed as not responding.
Most often the freeze is instant, sometimes I get to click a few times on “next” before it happens. I had it on simple nodes like Branch or Casts.
I looked at the log and the last entries are basically a bunch of “Can’t call UnrealScript […] while stopped at breakpoint.” which as far as I know should not cause issues. Most of them are UMG related.
I recently upgraded my project to 5.1.2 and see the same thing. Once it stops at a blueprint it freezes trying to pull up some search widget constantly. It makes debugging not work well. Hopefully someone from Epic has a fix for this.
I’m having this same issue in 5.2. I tried using pulling the same project from the market in 4.27 and have no issues, the breakpoints don’t cause any freezing but it seems to hang when pulling up variable info for sometimes up to 30 minutes. Since I cannot downgrade my main project to 4.27 the only other option is to start over, which I really do not want to do.
Try editing your UE5 Installation Options (via the Epic Games Launcher) and check that “Editor symbols for debugging” is enabled. Breakpoints should work as expected after it is installed.
https://github.com/EpicGames/UnrealEngine/commit/3d6246d201ffa0e7ce7480ac9deb8b0a55b59858
I dont understand what this means. Do you mean that we have to pull the engine from source and cherry pick a specific commit to our build just to get around this problem? Would this even work? What happens when the engine updates the version or adds fixes or something?
Try editing your UE5 Installation Options (via the Epic Games Launcher) and check that “Editor symbols for debugging” is enabled. Breakpoints should work as expected after it is installed.
This also does not fix this
There are other posts online that says you should downgrade to let the engine use DirectX11 and not DirectX12. This also does not fix this.
Link to other post:
Does anyone in the world has any information on this?
If the computer freezes or reboot for no good reason when/after using unreal, try using MSI afterburner to finetune your graphics card performance. Definitely seems like a bug with the engine.
Typical coding errors should only result in giving unreal error messages.
Upgrading to 5.3 may not be an option for some people.
I have found a workaround in 5.2 that in some limited use seems to reduce the frequency of the editor freezing, but doesn’t totally eliminate the problem in my experience.
Spread your blueprint nodes out from each other.
The workaround seems silly, but the more nodes next to each other around where the triggered breakpoint is at(ie too much spaghetti nodes) seems to increase the chances that the editor will freeze up.
