Search Issue Tracker
Fixed in 2019.1.X
Duplicate in 2018.3.X
Votes
0
Found in
2017.2.0b2
2018.1.0b11
Issue ID
1015876
Regression
Yes
Certain LINQ combinations yield wrong results on .NET 4.6
Reproduction steps:
1. Download user's project and open in Unity
2. Enter Play mode
Expected: in the console appears "a, b, c, d, e, f, g, h, i, j"
Actual: in the console appears "a, b, c, d, e, f, g, h, i, NULL"
Reproduced on: 2017.2.0b2; 2017.2.2p2; 2017.3.2f1; 2017.4.0f1; 2018.1.0b12; 2018.2.0a5
Not reproduced on: 2017.1.3p2; 2017.2.0b1
Regression introduced: 2017.2.0b2
Note: with .Net 3.5 works as expected
2017.2.2p2; 2017.3.2f1; 2017.4.0f1 actual result - "a, b, c, d, e, f, j, NULL, NULL, NULL"
Update:
Upstream issue https://github.com/mono/mono/issues/7696
-
Azim-Palmer
Oct 20, 2018 12:49
This is tragic. Makes me worry what other standard parts of the framework I can't use and they won't bother fixing.
-
ANTONBORODA
Sep 17, 2018 11:55
This is a disaster of an issue! How the hell is this postponed when 2013.3 marks .NET 3.5 as deprecated? This absolutely MUST be fixed before .NET 3.5 is removed.
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2019.1):
This issue has been fixed. Fix will be available in a future 2018.3 beta (likely b9) and a future 2018.2 version (likely 18.2.15).