Since updating my project from 4.24 to 4.25, UE started crashing a lot, seemingly at random, completely unrelated to what i am doing. It could be anything from compiling a blueprint to moving an asset in the level to just panning around; it just randomly decides to die with this error:
I tried reinstalling UE, verifying install, resaving project assets, even migrating all assets to a fresh 4.25 project, nothing. Both me and my colleagues are having the same issues since updating to 4.25…
Bump? Is no one experiencing this? Anything from the devs if they are aware of anything like this happening? I can’t be the only one affected by this, i found people telling me they are downgrading back to .24 for similar reasons…
Thank you for the suggestion. I installed debug symbols and i got a more detailed error, but still it looks to be caused by something inside the engine
I get a similar error. But I can’t even open my project, after its transition to version 25. I did not understand what it is connected with. My mistake or engine error.
What it is, seems like you have functions in graphs that use variable/references that does not exist anymore.
You’ve migrated a project without properly cleaning up “bad code” and the upgrade process caused a bug.
I would report a bug because corruptions like that should never happen no matter what the blueprint user does.
Shouldn’t that reflect in the error log? What are those references that no longer exist that you mention?
Again, what “bad code” exactly? If i had any errors to begin with i would have certainly noticed. Just to be sure though i went back and checked all blueprints and code, recompiling every blueprint individually, and everything came out clean (as expected).
I must also add that my project is 99% blueprint-based, so there shouldn’t be anything “mysterious” that may have happened without me noticing. Another fun fact is that when committing the changes after the update process to 4.25, it turns out the only file modified was the .uproject file, namely the version number present there. No other files were changed.
How can i submit a bug report with this? From what i gathered you cannot file bug reports yourself, you can just submit crash logs to epic when they happen, which i aleady did. Is there another way?
This what is happening to you is one reason why I avoid creating 100% blueprint projects.
I always keep a C++ base under the Blueprint types for safety purposes.
The fact that Blueprints are not text files (they are binary data) is very worrisome to go and make a full project based on graphs only.
On the other hand, C++ compilation is longer than blueprints and iteration suffer a bit when prototyping (so I’ve been researching, trying to find a way to add something in the middle).
Epic has been researching implementations of ‘text based’ blueprint assets for some years tho, but I’m sure that’s a hard thing to get done and make it production ready.
If Blueprints were already text files, when FKismetEditorUtilities::CompileBlueprint() is executed there, it could tell you with ease what exactly went wrong inside of your BP file instead of hard crashing your editor. Right now the way it is, you have to file a bug report using the bug report form and chase Unreal’s engineer to help, probably you’re going to need UDN access (paid support).
I’ve submitted a ticket, fingers crossed… I’ve also found a mention of a similar bug here, if anyone is interested. Also if anyone else has any other suggestions about what else can i try, I’m all ears.
I have been having the same issue. 4.21 is solid with no crashing, but couldn’t package. 4.24 and 4.25 I can package!! However, project crashes at random. Can’t wait to figure this out!
This Error is not happening to me in unreal 5.0.3 and I’m no longer able to open my project. It’s giving me the same error and I even tried creating a new project and copy over all my stuff but as soon as I do that it crashes my project and tells me “Unhandled Exception: EXCEPTION_ACCESS_VIOLATION writing address 0x00007ffccb7f1c90”
Update, I managed to open the project by moving all my content out of the project then creating a new map because the map was referencing my character which was crashing it everytime I tried to open it. Once I changed the starter map I brought the content back in but I’m still getting the same error message when I try to package my game on my phone.