Deleting a Blueprinted GameInstance causes Stack Overflow / Project Corruption

[Jambax]

Easy to reproduce:

• Create a GameInstance Blueprint in
  your project, then navigate to
  Project Settings > Maps and Modes >
  Game Instance.

  Set Game Instance to be your
  newly created Blueprint. Save and
  close editor (for good measure),
  then open editor again.

  Delete Blueprint GameInstance you
  created.

  Return to same location as above,
  and try to click on drop-down
  menu to select a new gameinstance.
  editor will Overflow trying to
  rebuild object list and crash.

This can potentially be serious if
user does not know how to
manually enter GameInstance in
DefaultEngine.ini file, or
doesn’t use source control. Its
impossible to recover from otherwise
and can effectively corrupt a
project.

[anonymous_user_33800a51]

Hey TheJamsh,

This appears to be related to crash in 4.8.1 that occurred when using any of World Settings GameMode override options. class caching was broken, leading to it getting stuck in a loop and overflowing stack. There are a few cases in which this still occurs after 4.8.2 hotfix that addressed that crash (UE-17673), and this looks like one of them. I can reproduce this following your steps in 4.8.3, but it’s been fixed internally and I can verify it’s already fixed in 4.9 Preview 2. Let me know if you see this happen again whenever you upgrade to 4.9.

Thanks!

[Jambax]

Nice Thanks !