Search Issue Tracker
Won't Fix
Votes
0
Found in
3.5.3f1
Issue ID
483471
Regression
No
Unloading native unity assets produces a crash
Won't fix:
Developers responsible for the area decided not to fix this issue, because addding safeguard preventing from unloading assets created/owned by the editor/engine is quite non-trivial in this case and there is a proper workaround of clearing the references of resources and using UnloadUnusedAssets instead.
To reproduce:
1. Create new project
2. Create c# script with following content:
Object[] textures = Resources.FindObjectsOfTypeAll(typeof(Texture));
for(int i = 0; i < textures.Length; i++)
{
if(textures[i].name == string.Empty)
{
continue;
}
if(textures[i].name != "LOADING")
{
Debug.Log("UnloadAsset: textures[i].name = "+textures[i].name);
Resources.UnloadAsset( textures[i] );
}
3. Attach it to camera and run
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment