All the people in this threat have a Ryzen processor. Could that be the source of the problem?
Problem solved in 5.3.2
User further up stated 5.3.2 did not fix the problem. Have you changed CPU’s by chance or anything else since first reporting?
im having the same issue, I’m using ue 5.3.2 as well
Confirmed with a few others too, 5.3.2 does not solve the problem. Whatever was fixed for you must have been something else. If you figure it out, please share!
My “solved” problem looks like the guy that said that his problem wasn’t fixed. First time i call the menu, it is slow to load. But that is a different problem to what I had. My engine just froze for 4-5 seconds. Additionally, after 5.3 while the first time i call the menu, things are slow, if I call it again, everything is fine.
I did not change anything other than the game version. I tested with 5.2, had the problem, installed 5.3 and the problem was gone.
Is your hard drive almost full by any chance?
So, the Context Menu has an option called Enable Non-Blocking Context Menu in Editor Preferences → General → Blueprint Editor Settings.
When that option is enabled, you will see the Context Menu loading with a loading bar. When its NOT enabled, it will freeze the editor and show nothing until the Context Menu is done loading.
That being said, it taking any time at all for me is not the norm. I had a massive project before and it took zero time for the Context Menu to load in UE4, and that’s not the case now in UE5. I’ve got plenty of free space on my SSD where UE is loaded.
Part of me did wonder if somehow the Context Menu is being loaded into the Page Cache instead of normal memory and that maybe somehow that’s part of the issue, but not sure. I still think given how few people its affecting compared to the overall community, it has to be a specific environment issue.
1 Like
Indeed. Disabling Enable Non-Blocking Context Menu brings back the problem. That said, Enable Non-Blocking Context Menu makes the loading faster. Which is good enough for me, but I am interested in solving the problem.
Enabling Non-Blocking Context Menu definitely helps speeds things up significantly, depending on what function you’re looking for you may still have to wait a few seconds before the results turn up.
I also noticed stalls when opening a new blueprint from the content browser, don’t know if any of you noticed those slowdowns.
bump
bump
BUMP. Please someone address this properly, it’s such a burden.
Bump. Long load times for Blueprint context menu. Everything else runs quick, but this content menu (Set to non blocking), loads (with blue load bar) for like 20-30 seconds. I thought maybe it would happen like once or twice and then cache actions in memory, but every time I open it it takes 20-30 seconds. Real workflow killer… 
This is in the base first person shooter project.
1 Like
Bump