Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.20
Issue ID
ADDR-3642
Regression
No
Crash on in __pthread_kill when requesting an Addressable Asset without adding it to an Addressable Group
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/boot.unity” Scene
3. Enter the Play Mode
4. Wait for a minute
Expected result: The Editor does not crash
Actual result: "UnityEngine.AddressableAssets.InvalidKeyException: Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown. No Location found for Key=StarsProgressPanel" exception is thrown and the Editor crashes after a while
Reproducible with: 1.21.12, (2022.3.4f1, 2023.2.0b5), 1.21.20 (2022.3.21f1, 2023.2.13f1)
Could not test with: 1.21.20 (2021.3.36f1 (“ArgumentException: The Object you want to instantiate is null" error is thrown), 2.0.3 (2023.2.13f1), 2.0.8 (2023.2.13f1, 2023.3.0b10) (Assets do not load)
Reproducible on: macOS Sonoma 14.3.1 (Intel, M1 (user’s)) (Play Mode in Editor)
Not reproducible on: No other environment tested
Could not test on: macOS Sonoma 14.3.1 (Intel) (Runtime (Mono-Development, Mono-Release)) (Assets do not load)
Note: Reproducible regardless of the selected platform
First few lines of the stack trace:
#0 0x00000186dee0dc in __pthread_kill
#1 0xea41000186d31a40 in abort
#2 0x472d800186c48b08 in malloc_vreport
#3 0xdc5b000186c4c3f4 in malloc_report
#4 0x304d800186c60ebc in find_zone_and_free
#5 0xe6168001030a0c80 in MemoryManager::Deallocate(void*, char const*, int)
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
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
- Dynamic text is rendered in the background when it is inside the <font> tag
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.