Suspected race condition in blueprint name conflict checking

I’ve hit a set of related issues that smell an awful lot like a race condition to me. I tried ~10 times to reproduce after I hit the initial issue (named CrashOnOpen below) and was able to get the outcome I’ve called CrashOnRename twice. These are all with the release editor build of 4.4.0 from the launcher.

I’m happy to try to repro from our source build (minimal differences from Epic sources, as far as this stuff is concerned) to fish out whatever other debugging information you might find useful. I’m likewise happy to provide access to project or asset files if that’s helpful. That said, I probably won’t have the spare time to track down and patch the problem myself (hence creating this issue instead of a PR) – I’m going to stash the current project state in a git branch and start patching the asset file on disk until I can get it to load.


Repro steps:

CrashOnRename

  1. Create a project.
  2. Create a blueprint
  3. Create a custom event in the event graph, name it ‘Something’
  4. Create a function named OnSomething
  5. Try to rename ‘Something’ to ‘OnSomething’ – hit enter really quickly here.
  6. Watch the editor crash out, click submit ;-).

This process works for me ~20% of the time or so.

I’ve also managed to make a project unopenable with a similar issue:

CrashOnOpen

  1. Create a function named OnSomething
  2. Create a custom event named Something
  3. Watch the editor freak out and rename OnSomething to $$ OnSomething $$
  4. Not be able to interact with the properties of the function (“Graph not editable” in the details window)
  5. Close the editor
  6. Try to open again – boom, segfault.

Answerhub is apparently unfond of minidumps, so I’ve uploaded them (along with the logs from each case) over here.


EDIT: Fixed formatting.

Hi aberghage,

I was able to reproduce the first issue easily. I have entered TTP# 345417 in our tracking software and the developers will be looking into it further.

As for the second one, I couldn’t get it to reproduce but I believe it is directly related to the first issue.

Thank you for the feedback,
TJ

Happy to help. If you need any other associated data or project files, let me know!

Hi aberghage,

This has now been fixed in our newest internal build. You should see it corrected in a future update, possible 4.5.

Thanks, TJ

Knocking it out of the park as usual! Thanks!