Unreal 4.12.2 Crashes when editing node comment

Development Programming & Scripting Blueprint
, , , , ,
1

Hi Flip,

I believe I have been able to reproduce the crash that you described. Just to make sure, would you be able to post your crash report here, including the MachineId and/or EpicAccountId (those will help me to find your submitted reports) so that I can compare your crash report to the one that I received?

Tim

2

Unreal 4.12.2 Crashes when editing a new node comment in level blueprint and move mouse for a few seconds while key-in field is active with some text already typed (so during the edit, when there is already some text typed into the text box, but not ‘entered’), it happened by accident 3 times today and I’ve reproduced the crash 2 times just now before typing this report…

I’m not sure at exactly what point the mouse- or possible mouse-over-event triggers the crash but it’s enough to move it over the already open right-click menu for a few seconds (without clicking) and the crash will happen. Crash reports were sent. Hope this helps!

Steps to reproduce:

  • open level
  • Go into Level Blueprint
  • Right click a node
  • click Comment
  • Type text in the comment field
  • Move mouse over other Right-Click menu items for a few seconds

-Flip

3

Hi Tim, nice fast response and good to read you’ve possibly been able to reproduce it.

MachineId:B5ECA30B4515720185D8BFB8EA45D095

For the crash report, should I post the full contents of CrashContext.runtime-xml or Report.wer? Thanks!

The Crashcontext mentions:
Assertion failed: ParentIndex != INDEX_NONE [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Slate\Private\Framework\Application\MenuStack.cpp] [Line: 514] &nl;&nl;

-Flip

4

Hi Flip,

Sorry for not getting back to you sooner. I was actually about to leave the office yesterday when I saw your post and thought I would take a crack at reproing the issue, which turned out to be fairly simple. Thanks for the MachineId, I was able to use that to find the reports that you had submitted, and from there I was able to determine that this is actually something that has been happening for a little while now. We had ticket UE-29086 put in to investigate this a few months ago, and I am happy to say that it appears to have been corrected internally. Unfortunately I am not sure if the fix will make it into 4.12.

Tim

5

Thanks a lot Tim! Will have to spam the save button some more in the mean while… :wink: I do think having the comment option in the node right-click-menu snap to a new text field above the node right away instead of having to type in a field of the menu could avoid the problem to happen.

6

Just read the 4.12.4 hotfix list:
Fixed! UE-29086 Crash When Typing a Node Comment and Hovering Over the Alignment Option

Thanks a lot and keep up the great work!