I have run a few more tests on our end and I have taken a look at the DxDiag that was given, however I have not been able to reproduce issue on our end.
Additional questions:
I’ll check in a couple of days.
Crash is still there - in 4.15.2 and 4.16 preview.
I’ve found that deleting two nodes in my Character blueprint also causes the same effect (also they are causing errors when I try to use nativization).
My colleague advised me to delete cache from …/AppData\Local\UnrealEngine\4.15 which resolved many problems at work, but not for me, unfortunately.
Just realized that I should update graphic drivers - so after that I’ll try again.
Still crashing after drivers update.
Is there something more I can do? Like build 4.15.2 in debug?
After updating to 4.15.2 I’ve found new bug crashing editor - narrowed down to render to canvas (not reproductible in blank project, doesn’t appear on 4.16) so I am stuck with all this crashes.
Additional suggestions:
If you migrate your assets to a clean project does this crash still occur?
Could you try the “Refresh Nodes” options on the widget causing the crash?
If I use “Refresh nodes” Editor crashes.
In my project - on startup, but in migrated content based copy-project - it didn’t crashed on startup but when I pressed “restore closed windows” (or similar - don’t remember exact command) then it crashed.
I tried that again - Editor loaded, no option to bring back closed windows, so I tried to open blueprint manualy - and then it crashed.
So basically it crashes always on opening this blueprint (even after refresh nodes).
It crashes even when I try to bring context menu over this blueprint.
Could you provide the complete callstack from the crash reporter window (including machine ID)?
Could you try using the fix up redirectors feature?
I had only 2 redirectors - but fixing them didn’t help.
Also I’ve updated today to 4.15.3 - but it is still crashing
I just wanted to clarify that you were not seeing the crash in the latest 4.16 (4.16.1 as of post (06/06/17))?
Bug still present in 4.16.1
Hello,
After extensive testing, we have been unable to reproduce this issue on our end. Without a reproducible test case we are unable to move forward. I will be marking this post as resolved for tracking purposes. However, if at anytime you are able to provide a reproducible test case please feel free to reopen this issue and I will be happy to take look.
Thanks,
I am happy to hear that you were able to workaround your issue. As stated above it the issue returns and you have more information on how to reproduce this issue please feel free to reopen the thread with more information.
Make it a great day
I’ve fixed this bug by recreating this widget.
After that Some other widget was still crashing, but for some time it doesn’t do that anymore.
For now everything is working