Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Votes
1
Found in
2018.1.1f1
Issue ID
1043171
Regression
No
[UWP] IL2CPP project failing to P/Invoking into ETW logging functions
Steps to reproduce:
1. Download attached project
2. Change platform to UWP
3. Build project with IL2CPP backend
4. Launch VS solution
5. Run project on a local machine (Debug and x64 platform)
Actual results: Unhandled exception is thrown due to improper IL2CPP conversion
Exeption: Unhandled exception at 0x00007FFAC454709B (ntdll.dll) in MSALCrashIL2CPP.exe: 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x0000002E0E803FD8).
Reproduced with: 2018.3.0a1, 2018.2.0b8, 2018.1.5f1, 2017.4.5f1, 2017.2.3p1
Not reproducible on .NET backend
Comments (2)
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
jpaiva-msft
Jun 15, 2018 23:23
More details here: https://forum.unity.com/threads/uwp-assemblies-not-working-when-using-il2cpp-but-work-on-net-scripting-backend.533401/
jpaiva-msft
Jun 15, 2018 23:22
There is also a P/Invoke to kernel32.dll!GetNativeSystemInfo that crashes on IL2CPP, unlike on .NET backend that prevents Microsoft.Identity.Client.dll from functioning properly.