Crash using the same CurveFloat on a variable and a timeline

Branch: Binary
Build version: 4.2.1-2101290

I get crash when using the same external CurveFloat on a timeline and a variable in the same blueprint. If I add a CurveFloat variable and point it to the same external curve as one of my timelines, it sometimes crashes when compiling or after I save and reload the project. If I do the other way around and change the timeline’s curve from internal to external, I get a crash as soon as compiling. Here’s the dump and logs Logs.zip

I’ve tried to replicate the crash on a blank content-only project and I simply can’t. I managed to run my project on 4.2.1 from GitHub and got a callstack from the crash when compiling after pointing my timeline track to the external curve: callstack.txt

Howdy pedro_clericuzzi,

Thank you for your bug report. I just had a couple more question that will help us to pinpoint what the issue is. Could you follow this template about how to report a bug? This will provide a better look into what is occurring. Here is a link to the template: How do I report a bug? - Programming & Scripting - Unreal Engine Forums. Could you also provide any screenshots of how you are setting up your blueprint or the CurveFloat timeline? Any additional information you could provide would be great.

Thanks and have a great day!

I edited the post to include additional information

Hi pedro_clericuzzi,

Thank you for updating your original post. I am a still a bit lost on the correct setup I would need to produce this issue. If possible, could you provide a couple of screenshots as to how you have been able to setup and crash the editor? Also, does this crash just occur on this one project or have you seen a similar crash with another? Any additional information would be greatly appreciated.

Thanks and have a great day!

Hi,

I get this crash only in my project. I did some more testing, created a copy of the CurveFloat asset and replaced the old one by it in both the variable default and in the timeline and it worked.

I thought the asset might have some sort of problem, but I couldn’t reproduce the crash using the same asset on an empty project, so maybe it was a reference problem somewhere? I know how annoying such kind of elusive bug can be, sorry for not being able to provide any more useful information.

Howdy pedro_clericuzzi,

Thank you for your bug report. I have been unable to reproduce the issue that you have been seeing. I have written a bug report so that the issue may be looked into further based on your callstack and your log files. Though it may not be addressed right away, it may be looked into and fixed in a future release.

Thanks and have a great day!

Hi pedro_clericuzzi,

I believe I may have resolved this issue in changelist 2229915 if you would like to test against that. Failing that it should make it out in release 4.4. Please update this thread if you continue to have issues.

Cheers

Ben.

I’m glad the callstack helped. Unfortunately, I deleted the offending curve a long time ago and have no means to test it anymore. I managed to get around the issue by creating a new curve asset and using it instead. For some reason, that worked.