Search Issue Tracker
Fixed
Fixed in 2.7.6
Votes
0
Found in
2.7.3
Issue ID
UUM-131139
Regression
Yes
[Addressables] Error "Destroy may not be called from edit mode! Use DestroyImmediate instead." is thrown when exiting the Play Mode
Reproduction steps:
1. Open the attached “IN-116318” project
2. Open the Package Manager window (Window > Package Manager)
3. Make sure a custom Addressables package isn’t used
4. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
5. Create a new build (Build > New Build > Default Build Script)
6. Enter the Play Mode, pause and unpause it
7. Observe the Console window or the Editor.log
Expected result: No errors are thrown
Actual result: “Destroy may not be called from edit mode! Use DestroyImmediate instead.” is thrown
Reproducible with: 1.22.2 (2022.3.66f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1), 1.27.0 (2022.3.66f1), 2.7.3 (6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1)
Not reproducible with: 1.21.21 (2022.3.66f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Repeat step 6 in-case the error does not show up
- The error is too big, so it is added in the internal comments
- A workaround is provided in the internal comments, by changing the Addressables “AtlasSpriteProvider.cs” code
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Silent crash when importing SVG files
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
Add comment