Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Votes
0
Found in
2022.3.60f1
6000.0.44f1
6000.1.0b12
6000.2.0a7
Issue ID
UUM-101315
Regression
No
Editor crashes on PrepareSpriteTilingData when exiting Play mode
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Make sure Sprite Atlas Mode is set to v2 - Enabled (Project Settings > Editor > Sprite Atlas > Mode)
5. Click “Tools > Add SpriteAtlases To Build”
6. Click “Tools > Build AssetBundles”
7. Click "Tools > Remove SpriteAtlases From Build"
8. Enter the Play Mode
Expected result: The Editor continues to run
Actual result: Editor crashes
Reproducible with: 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7
Reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
First few lines of Stacktrace:
0x00007ff641654a26 (Unity) PrepareSpriteTilingData
0x00007ff64190bb31 (Unity) SpriteRenderer::RendererCullingOutputReady
0x00007ff64177f5e4 (Unity) DispatchGeometryJobs
0x00007ff6419506a4 (Unity) CullScriptable
0x00007ff640eadffb (Unity) ScriptableRenderContext_CUSTOM_Internal_Cull_Injected
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 6000.1.0b15):
Fix for this issue is available on Unity 6000.1.0b15 and above
Resolution Note (fix version 6000.0.47f1):
Fix for this issue is available on Unity 6000.0.47f1 and above