Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0b1
2019.2.0a2
Issue ID
1123751
Regression
Yes
[UWP] Running the Player fails with access violation in unity_sequence_point_active_entry
How to reproduce:
1. Open the attached "SrpTest.zip" project
2. In Build settings, make sure that Script Debugging is enabled
3. Set target Device to "Any device" and build the project for UWP target platform
4. After building finishes, open the .sln solution file in the Visual Studio
5. Run the build on Local Machine with Master | x64 options
Alternative steps:
1. Open the attached "SrpTest.zip" project
2. In Build settings, make sure that Script Debugging is enabled
3. Build the project for UWP target platform
4. After building finishes, open the .sln solution file in the Visual Studio
5. Run the build on Remote Machine (HoloLens) with Master | x86 options
Expected result: No exceptions thrown.
Actual result: An exception is caused by unity_sequence_point_active_entry when accessing event_requests which is nullptr.
Reproducible with - 2019.1.0b1, 2019.1.0b3, 2019.2.0a2, 2019.2.0a5
Not reproducible with - 2018.3.5f1, 2019.1.0a15, 2019.2.0a1
Note:
- The access violation occurred only when Script Debugging was enabled (in the Build Settings).
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
- Screen.SetResolution() ignores width and height parameters when switching from Fullscreen to Windowed mode
- Crash on il2cpp::vm::Class::Init in the Player when handling FileNotFoundException in cascading catch blocks in async method
- Mesh with vertex animation shader renders incorrectly when using DirectX11 and AMD GPU
- Select Dependencies context menu doesn't work properly in Project Browser
- List of supported Platforms for 3D Templates in Unity Hub is outdated
Resolution Note (fix version 2019.1):
Fixed in 2019.2.0a8
Backported to 2019.1.0b7