Search Issue Tracker
Won't Fix
Votes
4
Found in
2017.1.0f3
Issue ID
948737
Regression
No
"Assertion failed: ReleaseAllScriptCaches did not release all..." error is thrown when calling 'AssetDatabase.LoadAssetAtPath'
How to reproduce:
1. Open users attached project
2. Open the "DialogueConditionLanguage" script, observe that it is calling 'AssetDatabase.LoadAssetAtPath' from within OnBeforeSerialize()
3. Go to File --> Build Settings
4. Build the project
Expected result: Project gets built, no errors are thrown in the console
Actual result: Project gets built, "Assertion failed: ReleaseAllScriptCaches did not release all script caches!" error is thrown
Reproducible with - 2017.3.0a7, 2017.2.0b11, 2017.1.1p1, 5.6.3p3
Comments (1)
-
FWCorey
Nov 20, 2017 01:53
Also happens in 5.5.2f1 but crashes the Editor every second or third script import.
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
- 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
Resolution Note:
Unity APIs should not be called from within OnBeforeSerialize, but it is allowed, otherwise we would break a lot of projects. The real solution is to provide another mechanism to solve the problem the user is trying to solve in this project.