Description

I had to force quit the editor when it was taking too long to shut down, and it appears some assets got saved incorrectly. Probably nothing that can be done about the assets being saved incorrectly, but attempting to start the editor again crashed until I deleted the invalid assets.

Having one invalid asset shouldn't prevent you from launching the editor. Instead the editor should launch as normal but the problematic asset just shouldn't be available. An error message should be displayed identifying the invalid asset and telling the user it should be deleted or restored from a previous version in source control.

Steps to Reproduce
  1. Attempt to open attached project
  2. Observe crash
Callstack
Assertion failed: InPos <= Size [File:D:\P4\Release-4.16\Engine\Source\Runtime\Core\Private\HAL\FileManagerGeneric.cpp] [Line: 623] 
Attempted to seek past the end of file (170637/3012), file: ../../../../../Unreal Projects/InvalidAsset/Content/ch09_textureblend/Materials/MI_Wall.uasset. The file is most likely corrupt.


>	UE4Editor-Core.dll!FArchiveFileReaderGeneric::Seek(__int64 InPos) Line 623	C++
 	UE4Editor-AssetRegistry.dll!FPackageReader::ReadAssetRegistryData(TArray<FAssetData *,FDefaultAllocator> & AssetDataList) Line 137	C++
 	UE4Editor-AssetRegistry.dll!FAssetDataGatherer::ReadAssetFile(const FString & AssetFilename, TArray<FAssetData *,FDefaultAllocator> & AssetDataList, FPackageDependencyData & DependencyData, TArray<FString,FDefaultAllocator> & CookedPackageNamesWithoutAssetData, bool & OutCanRetry) Line 852	C++
 	UE4Editor-AssetRegistry.dll!FAssetDataGatherer::Run() Line 595	C++
 	UE4Editor-Core.dll!FRunnableThreadWin::Run() Line 76	C++
 	UE4Editor-Core.dll!FRunnableThreadWin::GuardedRun() Line 25	C++
 	[External Code]	

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-45762 in the post.

0
Login to Vote

Won't Fix
ComponentUE - Foundation - Core
Affects Versions4.16
CreatedJun 7, 2017
ResolvedAug 18, 2021
UpdatedAug 18, 2021
View Jira Issue