Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2018.4
2020.1.0b2
2020.2
Issue ID
1228829
Regression
No
[IL2CPP] Dispose is called before the value in the 'using' statement goes out of scope
To reproduce:
1. Open the user's attached project
2. Build and run on Android
3. Observe the logcat
Expected: Dispose is called only when the value in the 'using' statement goes out of scope
Actual: Dispose is incorrectly called each time in the while(true) loop
Reproduced with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Reproduced with:
VLNQA00231 Huawei HUAWEI Mate 20 Pro 9 HiSilicon Kirin 980 Mali-G76 OpenGL ES 3.2 LHS7N18B15013748
VLNQA00279 Samsung Galaxy S10+ 9 Snapdragon 855 SM8150 Adreno (TM) 640 OpenGL ES 3.2 R58M22D67PX
VLNQA00160 iPhone 6S iOS 13.3.1
Not reproducible with Mono
Notes: could not build on Mac Standalone + IL2CPP scripting backend due to an error.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment