Search Issue Tracker
Fixed in 4.6.1
Votes
1
Found in
4.5.4f1
Issue ID
639987
Regression
No
AssetBundle.Unload errors
-e: On Linux, you can't call AssetBundle.Unload(false) at all. The first call will report: "AssetBundle.Unload(false) shouldn't be called..." error. If you follow it up with an additional "CreateFromFile" call, you will get a "Asset Bundle cannot be loaded because another asset bundle with the same name is already loaded." error.
Works well on Win & OSX
-repro:
--build attached project as dev version
--copy the bundle into the Data folder
--run build
--click Load Asset
--click Unload Asset(false)
--NOTICE error being thrown
--click Create Instance
--NOTICE error begin thrown
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
- Transform corruption and/or crash on PhysX::CreateCharacterController when spawning physics objects into Prefab stages
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
Add comment