Constant crashes in Blueprints

I cannot do anything other than looking at Blueprints. As soon as I try to display class settings, class defaults, or if I create a variable (directly or via “Promote to a variable”), it crashes. Everytime. I tried new projects (C++, Blueprint), and projects converted from 4.7.5. Same thing.

It’s such a major bug (and yes, I rebooted my computer). Am I the only one with this issue?

I get the following error (full log attached):
Unknown exception - code 00000001 (first/second chance not available)

"Assertion failed: IsValid() [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.8\Engine\Source\Runtime\Core\Public\Templates\SharedPointe

Hi ,

I haven’t been able to reproduce this on my end. Can you upload the full crashlogs (the file you uploaded is the callstack)? They are located at \Unreal Projects\PROJECTNAME\saved\logs. The steps I took to try and reproduce this were:

  1. Open project (any)
  2. Create new actor BP
  3. Go into event graph
  4. Right click begin overlap event “Other Actor” pin>Promote to variable
  5. Open Settings
  6. Open Defaults
  7. Change settings in either settings or defaults
  8. Compile
  9. Attempt steps 3-8 with Character BP as well.

Are there any steps you are taking that I am not? I’m happy to continue attempting to reproduce this error so we can get it quickly resolved.

Thanks . I’m aware that it must be something specific with my config. I asked a colleague and she does not have any issue on her side. But it’s reproducible, even after a . If I create a new Blueprint blank project, right click in the content browser, new Blueprint class, I inherit from Actor, then in the event graph of this class, if I click on “add new variable”, it crashes. And I still have no issue whatsoever with 4.7.5.

I removed the installation of 4.8 and I’m currently doing another install. I will let you know.

In the meantime, I attached the full log you requested. link text

I re-installed 4.8 but still the same thing. I followed the steps you described , step 4 crashes for me.

This is the full log of the brand new blank Blueprint project I created after a fresh install of 4.8 P2 after the crash I got at step 4:

link text

Can you post your dxdiag? While I highly doubt it it may be hardware specific so I’d like to rule this out as a potential option.

Sure. Here it is.

link text

Try updating your video card drivers to see if that helps any. I’m not certain it will help but it certainly can’t hurt to try! I’ll keep trying to reproduce on my end.

I updated my graphics driver to the latest (NVIDIA 350.12). Still the same problem. I may have a somewhat particular configuration, for instance I don’t have sound (my computer does not have any audio card). And I have the latest Oculus runtime (0.5.0.1) installed. I don’t know why it would affect the Blueprint editor but… I thought I would mention it in case you guys made changes related to audio or/and Oculus in 4.8. Besides that, I don’t know what can I try… It’s obviously a blocker, I cannot use 4.8 preview 2 (the first preview was fine). Thanks for trying . I will keep doing tests on my side.

We tried running this test on one of the pc’s here that has Oculus set up with the .5 SDK installed and did not reproduce the crash. Is there anything else specific to your pc that could be causing this error? Do you have permissions set up for your firewall? I honestly can’t think of anything else that would cause this kind of crash on one pc but no others, it’s a bit bizarre.

I agree, it’s bizarre. It still works fine with 4.7.5 and 4.8 preview 1 worked great too. I just finished compiling the editor from source to get a closer look.

I tested with the editor compiled from source (tagged 4.8 taken yesterday at revision 651c353759588a46d8b25cd815a12ddcf3ffbeb8) and I have no problem! So I don’t know what to think of it. Technically it’s not the same project though since it forced me to make a copy of it (as it detected it was not the same version, but that might be normal between a binary version and the one compiled from source). I hope preview 3 will make this things disappear.

That is good that the github build doesn’t crash on you. For now, lets hold off until Preview 3 to see if you get the same errors there. I’ll leave this question open until then so we can test and see if you have any further errors.

Thank you so much for trying . Since I’m curious I’ve downloaded the preview 2 from github, compiled it, and tried it. It detected that the project was not the same version (which I found weird since they are actually the same), I converted my project in place, and I have no problem! So there’s something weird about the binary preview 2 I have (even though I tried to re-install it already). Very weird. It’s the type of problem where you never know what it is. Anyway, it will probably be fixed by itself with preview 3 in a few days. In the meantime I will use the preview 2 I compiled from source.

Just one question: why did it detect it was a different version? If I commit some changes done with my preview 2 from source, will my colleagues have problems with my files using the binary preview 2??

As long as they are both preview 2 they should be fine to transfer between.

I tried Preview 3 and it still the same issue for me. Here what I did:

  • Uninstall preview 2
  • Install preview 3
  • Create a new Blueprint project
  • Right-click in content browser, new Blueprint class inhering from Actor
  • Trying to open ‘Class settings’ tab is enough to crash

I attached the full log.

Hi morpph208,

Opening the class defaults/settings causing a crash is a known issue and has been reported under UE-15837.

Ah ok. Good to know. It means that it will be fixed at some point. Any hint on what would be the cause? Do I have a workaround in the meantime?

Unfortunately no, we found it maybe ten minutes before I responded here. However, it is a blocker so once it gets assessed it will probably be quickly fixed so developers can continue working.

I can confirm this. Got crashes every 1-2 minutes or so after converting a project from 4.7.6 to 4.8 Preview 2.

Yes, that’s the thing. I made the test on a new computer with 4.8 preview 3. At first, it worked fine. But it stopped working after a while. Not sure why or how it occured. Did I have a limited number of click, an amount of time or did I do anything in between that triggered the bug, I don’t know.