UWrangleContentCommandlet critical error

Development Platform & Builds
, , , , ,
1

When I try to execute the UWrangleContentCommandlet via ue4editor-cmd.exe, it throws me this error:

[2017.08.10-15.18.01:228][  0]LogContentCommandlet: Warning:
[2017.08.10-15.18.01:228][  0]LogContentCommandlet: Warning: Saving unreferenced objects [1457 packages]:
[2017.08.10-15.18.04:308][  0]LogWindows: Error: === Critical error: ===
[2017.08.10-15.18.04:309][  0]LogWindows: Error:
[2017.08.10-15.18.04:310][  0]LogWindows: Error: Assertion failed: MovedPackage [File:D:\Build\++UE4+Release-4.17+Compile\Sync\Engine\Source\Editor\UnrealEd\Private\Commandlets\ContentCommandlets.cpp] [Line: 2206]
[2017.08.10-15.18.04:312][  0]LogWindows: Error:
[2017.08.10-15.18.04:313][  0]LogWindows: Error:
[2017.08.10-15.18.04:314][  0]LogWindows: Error:
[2017.08.10-15.18.04:315][  0]LogWindows: Error: KERNELBASE.dll!0x0000000067369E08
[2017.08.10-15.18.04:316][  0]LogWindows: Error: UE4Editor-Core.dll!FOutputDeviceWindowsError::Serialize() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\core\private\windows\windowsplatformoutputdevices.cpp:120]
[2017.08.10-15.18.04:320][  0]LogWindows: Error: UE4Editor-Core.dll!FOutputDevice::Logf__VA() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\core\private\misc\outputdevice.cpp:70]
[2017.08.10-15.18.04:322][  0]LogWindows: Error: UE4Editor-Core.dll!FDebug::AssertFailed() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\core\private\misc\assertionmacros.cpp:349]
[2017.08.10-15.18.04:325][  0]LogWindows: Error: UE4Editor-UnrealEd.dll!UWrangleContentCommandlet::Main() [d:\build\++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\commandlets\contentcommandlets.cpp:2209]
[2017.08.10-15.18.04:329][  0]LogWindows: Error: UE4Editor-Cmd.exe!FEngineLoop::PreInit() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\launchengineloop.cpp:2134]
[2017.08.10-15.18.04:331][  0]LogWindows: Error: UE4Editor-Cmd.exe!GuardedMain() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\launch.cpp:127]
[2017.08.10-15.18.04:334][  0]LogWindows: Error: UE4Editor-Cmd.exe!GuardedMainWrapper() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:134]
[2017.08.10-15.18.04:336][  0]LogWindows: Error: UE4Editor-Cmd.exe!WinMain() [d:\build\++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:210]
[2017.08.10-15.18.04:340][  0]LogWindows: Error: UE4Editor-Cmd.exe!__scrt_common_main_seh() [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253]
[2017.08.10-15.18.04:342][  0]LogWindows: Error: KERNEL32.DLL!0x00000000683B2774
[2017.08.10-15.18.04:343][  0]LogWindows: Error: ntdll.dll!0x000000006A3B0D51
[2017.08.10-15.18.04:344][  0]LogWindows: Error: ntdll.dll!0x000000006A3B0D51
[2017.08.10-15.18.04:345][  0]LogWindows: Error:
2

The full command is:

"B:\Epic Games\UE_4.17\Engine\Binaries\Win64\UE4Editor-Cmd.exe" "A:\Projekte\Unreal-Engine-4-Projekte\ISTS\ISTS.uproject" -run=WrangleContent -allmaps

If needed, I can provide the full log.
Also, what is the now preferred way of stripping old content? I always assumed that this command is the right way.

3

Hi ,

Unfortunately the UWrangleContentCommandlet isn’t really used much any more. Would you be able to provide the full command that you are running?

4

Hi ,

Sorry for not getting back to you sooner. I was still able to see the issue that you were running into in 4.18. We had previously had a ticket to have this commandlet deprecated, but that ticket has since been closed without any work being done on it. That would seem to indicate that the commandlet was still intended to be used, so I have entered UE-55802 to have this investigated further.

5

This is still an issue in 4.20.3.

I got the same basic critical error and assertion. We desperately need a real cleanup tool- I can’t even just get it to write a .CSV of files for us to clean up manually.

Is there ANY movement on this?

6

Okay, if I add the -restore flag and run again after the crash, I can at least get a partial text log of unused files, which I can > redirect to a file.

It’s nowhere NEAR as useful as a .CSV, but it’s something.