It’s the 10th time my editor crashes, because I change a variable type no matter from which type to which one I change. The variable isn’t even in use, the “get” node is just floating around but it still forces to crash the damned editor. 2 hours of work is completely gone now, because I couldn’t even save so fast this time!
Hello,
- Could you provide your logs from your project’s Saved->Logs folder?
- Could you please provide your Machine ID from the Crash Reporter window, as well as ensure you press send on the report?
- Do you have any repro steps we can follow to reproduce this issue in a clean project?
Of course. There are two logs created at the same time, so I upload them both.
My machine ID: 86427E0A41D7B6064C0C20B5D7E1B091
And this is what stands in the crash reporter:
“Access violation - code c0000005 (first/second chance not available)”
Everytime this error occurred:
- I have created a variable in the level blueprint
- I placed the get or set node from this variable in the level blueprint
- I changed the variable type for example from float to integer or something else
- The editor asked if I really wanted to change the variable, because it is in use
- I clicked okay and the editor began to be slower until it crashed
Thank you for the information. I have attempted to reproduce the issue using the steps you’ve provided above in a clean project, but I wasn’t seeing the same error.
Could you please provide your dxdiag, and also try the repro yourself in a clean project to see if you are able to get the same crash?
Since this issue is project specific, could you please zip up the project and provide me with a link to Dropbox where I can download it? You can provide the link in a PM on the forums if you’re concerned about keeping the project private. Here is the link: https://forums.unrealengine.com/member.php?160394-Sean-Flint
I tried to reproduce the issue in a clean project and I also wasn’t seeing the error this time. But I can’t really find a reason for this issue if it is only occurring in this project.
I also tried to reproduce the issue in my current project and there it still crashes no matter in which blueprint I change the variable…
Alright. Thanks for your help, I’m going to upload it now but it can take a while, because it’s a pretty large project although it is just to get started with the engine…
You say that the project begins to run slower until it crashes. Could you please open up your task manager during this time and note the memory usage of UE4? Let me know if you notice any memory spikes during this time.
I have attempted to reproduce that issue on my end, but I haven’t been able to do so in a clean project. I’m assuming that the blueprint that you are changing the variable type in is quite complex? If this is the case, that would explain why the memory usage jumps. Would it be possible for you to attempt to just PM me the .uasset file of the blueprint that you are having this issue with? I could attempt to migrate it into a new project and see if I get the same memory issue and crash.
You’re a genius. Normally the usage is about 2GB…When I changed the variable type it got up to 11GB…
This issue sadly occurrs with all of my blueprints no matter how complex it is…I also tried creating a new level and tested this issue in a clean blueprint. The result was the same. But if you want I can send you some of my blueprints.
You could either send the blueprints to me, or you could attempt to migrate a few of them into a clean project and see if you’re getting the same memory issue and crash in that project using the same blueprints. If you decide to do the latter, let me know what results you see.
I migrated the blueprints in a clean project and tried to reproduce the issue.
Oddly, the memory still got higher (about 20 MB per change), but it did not go further - it just stopped.
So you’re not seeing the same behavior in a clean project? If this is the case, then it is possible that it is something specific to your project.
I would say that it’s worth a try. While it may not solve your issue, it will determine whether the project became slightly corrupted somehow, or if there is some issue with the blueprints themselves. Let me know the results after you are able to migrate the files over.
I think so, too. Do you think it’s worth it to try to migrate all project files into a clean project? Or should I simply try not to cause this issue by removing the nodes before changing the value type?
It seems that the issue is connected to the project somehow. Now the memory only gets higher if I repeatedly place and change the variables but as in the recent try it doesn’t go as high as in the beginning. I’m okay with this, because it would take too long to find out what causes the issue and it seems to be a project problem.
I’m using the “new” project now and be careful with the variables. Thanks for your help!