Search Issue Tracker
Fixed
Votes
0
Found in
2023.2.14f1
2023.3.0b10
6000.0.0b11
Issue ID
UUM-66162
Regression
Yes
Crash on OutputImporterLogsForArtifact when opening a specific project
Steps to reproduce:
1. Open the “users attached project”
2. Observe the crash
Reproducible with versions: 2023.2.0a17, 2023.2.14f1, 2023.3.0b10
Not reproducible with versions: 2021.3.36f1, 2022.3.21f1, 2023.2.0a16
Reproducible on: macOS Sonoma 14.3.1 (Intel), Windows 11 (by the reporter)
Not reproducible on: no other environment tested
First few lines of Stack Trace:
{noformat}
0x00007FF91829635C (Unity) OutputImporterLogsForArtifact
0x00007FF918292828 (Unity) AssetImportManager::Import
0x00007FF918270B3F (Unity) ImportOutOfDateAssets
0x00007FF91827A71F (Unity) RefreshInternalV2
0x00007FF918283A7A (Unity) StopAssetImportingV2Internal{noformat}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14959