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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment