Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2018.4
2019.1.10f1
2019.2
2019.3
2020.1
Issue ID
1210526
Regression
No
Crash when calling PrefabUtility.SaveAsPrefabAsset with a absolute path that is outside of project's root
How to reproduce:
1. Open user-submitted project (ForDebugging.zip)
2. Open the SampleScene
3. Enter Play Mode
4. Click the 'Save' UI button
5. Save a prefab to a path, that is outside of the project's root path
Expected result: the Editor does not crash
Actual result: the Editor crashes
Reproducible with: 2018.4.16f1, 2019.2.19f1, 2019.3.0f6, 2020.1.0a20
Could not test with: 2017.4.36f1('UnityEditor.PrefabUtility' does not contain a definition for `SaveAsPrefabAsset')
-
unity_CyjrzFgo7Zyw3Q
Feb 20, 2020 11:51
Can confirm this issue in 2019.3.1f.1
Additional info: the runtime doesn't crash, i.e. no crash log is produced in %TEMP%\Unity\Editor\Crashes, the editor just closes.
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3