Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
1
Found in
2020.1.0b2
2020.2
Issue ID
1230447
Regression
Yes
[Mobile] ConcurrentBag.TryTake() throws exception in IL2CPP build
Reproduction steps:
1. Open the attached project "case_1230447-ConcurrentBagIssue-2020.1.zip"
2. Build on Android platform (IL2CPP)
3. See log via logcat4. You can see "NotSupportedException: linked away" instead of "Take true" or "Take false"
Expected behaviour : TryTake() return true or false.
Actual behaviour : TryTake() throws exception.
Reproduces on: 2020.1.0b2, 2020.2.0a5
Does not reproduce on: 2017.4.38f1, 2018.4.20f1, 2019.3.7f1, 2020.1.0b1
Tested on these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00140, Samsung Galaxy S4 (GT-I9505), Android 5.0.1, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320
VLNQA00160 iPhone 6S iOS 13.3.1
Notes:
-This issue does not reproduce with Mono backend or Editor.
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
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b9
Resolution Note (fix version 2019.4):
Fixed in 2019.4.1f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.24f1