Search Issue Tracker
Fixed in 5.3.7
Votes
0
Found in
5.3.4f1
Issue ID
801677
Regression
No
Unity crashes while importing 26000x26000 JPG file
Import the attached project. If the editor doesn't crash, do a Reimport All. The Editor will crash at this point with the following stacktrace:
0x000000014072F590 (Unity) DoesTextureContainAlpha
0x00000001407ED0A7 (Unity) TextureImporter::GenerateAssetData
0x00000001406E21DA (Unity) AssetDatabase::ImportAsset
0x00000001406F07EE (Unity) AssetDatabase::UpdateAsset
0x00000001407B4003 (Unity) AssetInterface::ProcessAssetsImplementation
0x00000001407B4C5B (Unity) AssetInterface::StopAssetEditing
0x0000000140709643 (Unity) VerifyAssetsForBuildTarget
0x0000000140C7AAFE (Unity) Application::InitializeProject
0x0000000140E3D0BF (Unity) WinMain
0x0000000141539330 (Unity) strerror_s
0x00007FFA38338102 (KERNEL32) BaseThreadInitThunk
0x00007FFA3A00C5B4 (ntdll) RtlUserThreadStart
Reproduced with Unity 5.1, 5.2, 5.3 and 5.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment