GetTimeRange crash on project startup

Thanks for the report. I’ll try to repro but if you’ve got a test project for me, I’ll be happy to look.

I’m in the midst of upgrading a small side project to 4.17 and I’m getting the following crash on load:

MapCheck: New page: Map Check
LightingResults: New page: Lighting Build
LogMaterial: Missing cached shader map for material M_Background, compiling. 
LogMaterial: Missing cached shader map for material M_Player, compiling. 
LogMaterial: Missing cached shader map for material M_SingleColor, compiling. 
LogWindows: Error: === Critical error: ===
LogWindows: Error: 
LogWindows: Error: Fatal error!
LogWindows: Error: 
LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000
LogWindows: Error: 
LogWindows: Error: UE4Editor-MovieScene.dll!FMovieSceneBinding::GetTimeRange() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\moviescene\private\moviescenebinding.cpp:16]
LogWindows: Error: UE4Editor-MovieScene.dll!UMovieScene::UpgradeTimeRanges() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\moviescene\private\moviescene.cpp:669]
LogWindows: Error: UE4Editor-MovieScene.dll!UMovieScene::PostLoad() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\moviescene\private\moviescene.cpp:728]
LogWindows: Error: UE4Editor-CoreUObject.dll!UObject::ConditionalPostLoad() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\coreuobject\private\uobject\obj.cpp:991]
LogWindows: Error: UE4Editor-CoreUObject.dll!EndLoad() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\coreuobject\private\uobject\uobjectglobals.cpp:1561]
LogWindows: Error: UE4Editor-CoreUObject.dll!LoadPackageInternal() [d:\build\++ue4+release

I tried migrating the assets to another project, this works in the sense I can boot up the project but if I open up a UMG asset that contains animations or references to animations it crashes.

I have attached the crash log to the post. Let me know if you need anything from me, happy to provide the project if it helps you to diagnose the problem.

Sent you a PM on the forums Max, thanks!

Great, thank you. That was perfect. I checked in the fix (CL#3592244) and it will be coming out in 4.17.2. If you need the details of the bug, you should be able to follow this link when it becomes available tomorrow:

https://issues.unrealengine.com/issue/UE-48490

i have the same problem.
what is link to the fix?

See the answer below, there’s the CL if you can compile the engine yourself. Otherwise, you’ll need to wait for the 4.17.2 hotfix.

so i have to wait until…