Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.5.0
Issue ID
ADDR-3981
Regression
No
Errors “Assertion failed on expression: 'm_PreventLoadingFromFile != nameSpaceID'“ and “UnloadAssetBundle failed“ are present when exiting Play Mode with the "Use Existing Build" mode selected
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/_PROJECT/Scenes/Rooms/SampleScene.unity” Scene
3. Enter the Play Mode
4. Exit the Play Mode
5. Observe the Console
6. Repeat steps 3-5 20 times
Expected result: No Errors exist
Actual result: Errors “Assertion failed on expression: 'm_PreventLoadingFromFile != nameSpaceID'“ and “UnloadAssetBundle failed“ are present
Reproducible with: 2.4.6 (6000.0.50f1), 2.5.0 (6000.0.50f1, 6000.1.4f1, 6000.2.0b3)
Could not test with: 2022.3.62f1 (Assets\Engine\Runtime\Audio\AudioChannelBase.cs(15,35): error CS0246: The type or namespace name 'AudioResource' could not be found (are you missing a using directive or an assembly reference?))
Reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- The issue only reproduces once in 20 attempts
- Does not reproduce in Player
- Not reproducible when using the AssetDatabase path
- The issue does not seem tied to any specific asset or bundle
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.