[BUG 4.11] Project crashes when attempting to undo a deleted function in UMG

This is a bug that i have encountered almost everytime. I created a simple fill color and opacity binding for a progress bar and whenever i delet it and then undo that action, it crashes.

Hello Xanadron,

I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  3. Can you reproduce this issue in a the latest release of the engine?
  4. Could you provide screen shots of any widgets/blueprints involved with this issue?

Hi, i have created an event dispatcher from MyCharacter’s BP so it can communicate with a widget. In that widget i have created a progress bar and a binding for fill color and opacity for that bar. The bug seems to appear when i first delet the function of that binding and quicly undo that. If i do not undo it and remove the binding after that the project doesn’t crash anymore. I haven’t tried this in a clean project and in the latest release.

After further testing, I was unable to reproduce this issue with the information provided. Could you try and reproduce this issue in a clean project? If you are able to reproduce this issue in a clean project, could you then go through and answer the questions asked above (as they pertain to reproduction in a clean project)?

Hi, i have created a project and the crash did not happen.

I think it was just an error in my engine. I will try it in the latest release but i don’t think it will happen because it didn’t happen here…

Hello Xanadron,

I see that you said you are going to run another test in the latest release. If after the test you have any additional information on how to reproduce this issue on our end let me know and I will be happy to follow up.

Hello Xanadron,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

Thanks,