Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.4.X
Votes
0
Found in
2017.2.2p3
Issue ID
1038465
Regression
No
[2017.x] [UWP] IL2CPP generates incorrect code for lock() statement in UWP non-development build
Steps to reproduce:
1. Download 1038465_repro.zip
2. Switch platform to UWP
3. Build with IL2CPP backend, non-development build
4. Build project in Visual Studios (Debug configuration, x64 platform, run on Local Machine)
Expected results: App runs without freezing
Actual results: App freezes after launch.
Reproduced with: 2017.4.3f, 2017.3.2f1, 2017.2.3f1, 2017.1.3p4
Not reproducible with: 2018.2.0b4, 2018.1.2f1
Not reproducible on a Development build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment