Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.6f1
2018.3.10f1
Issue ID
1141849
Regression
Yes
Crash on AssetImporter::GetAssetPathName when opening a project
How to reproduce:
1. Unzip the attached project from "case_1141393-MRTK.zip"
2. Open the project with Unity Editor
-- Editor crash
Reproducible with - 2018.3.6f1, 2018.3.12f1
Not reproducible with - 2018.3.5f1, 2019.1.0b5, 2019.1.0b10, 2019.2.0a10
Stack trace (one of possible):
(Unity) memcpy
(Unity) core::StringStorageDefault<char>::assign
(Unity) AssetImporter::GetAssetPathName
(Unity) AssetImporter_Get_Custom_PropAssetPath
(Mono JIT Code) (wrapper managed-to-native) UnityEditor.AssetImporter:get_assetPath (UnityEditor.AssetImporter)
(Mono JIT Code) [C:\buildslave\unity\build\Modules\AssetPipelineEditor\Public\PluginImporter.bindings.cs:181] UnityEditor.PluginImporter:InvokeShouldOverridePredicate ()
<...>
Notes:
- No crash on reopening the project again.
- Crashes with different stack traces (on "mono_add_process_object", "FindShaderPropertyIndex", "scripting_object_get_class", etc.).
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
- “Destroying assets is not permitted to avoid data loss” error thrown when creating a second Tile Palette Brush Pick Asset
- The “Copy to clipboard” button has no hover or click animations when hovering and clicking the “Copy to clipboard” button after selecting an issue from the “Code” tab of the Project Auditor window
- Saved Tile Palette Brush List items become malformed causing the list to become cut off when decreasing the Pick size with the slider
- Foldout triangle icons and the foldouts titles are not aligned/centered in the “Assembly” and “Areas” Filter windows of the Project Auditor window
- High MeshSkinning duration when using Vulkan
Resolution Note (2018.3.X):
According to the UpgradeGuide in MRTK-2017.4.3.0 package is targeting Unity 2017.x products.
# General Release Information
This release is targeted for the Unity 2017.x products
It seems like opening the project (that is using MRTK-2017.4.3.0 package) with Unity 2018.x may cause memory corruption due to the package incompatibility with Unity 2018.x products.
Please rather downgrade the project to Unity version to 2017.x version or upgrade the MRTK packagage to version 2.0.0-+ that targets Unity 2018.x products.