Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random crashes on HoloLens 2 related to OpenXR #11420

Closed
Suddelnuppe opened this issue Mar 17, 2023 · 3 comments
Closed

Random crashes on HoloLens 2 related to OpenXR #11420

Suddelnuppe opened this issue Mar 17, 2023 · 3 comments
Labels
Bug Feedback Request MRTK2 Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on

Comments

@Suddelnuppe
Copy link

Describe the bug

We experience random crashes on the HoloLens 2, that seem to originate from OpenXR. Updating both OpenXR packages in Unity didn't help. Neither did anything else we tried.

To reproduce

Unknown how to reproduce it. Seems to happen more often when the CPU is heavily used.

Expected behavior

No crashes

Your setup (please complete the following information)

  • Unity Version 2021.3.5f1
  • MRTK Version 2.8.1
  • HoloLens 2 updated to latest release

Target platform (please complete the following information)

  • HoloLens 2

Additional context

Here is the stack trace from the crash dump.

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffeafe5a088 (UnityOpenXR!session_RequestExitSession+0x00000000000020f0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

READ_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

STACK_TEXT:
000000ccec6fc7b0 00007ffeafe3a678 : 000000ccec6fc7f0 00007ffeafe3a678 0000026430af8710 0000000000000000 : UnityOpenXR!session_RequestExitSession+0x20f0
000000ccec6fc7f0 00007ffeafe3973c : 000000ccec6fc930 00007ffeafe3973c 000000ccec6fc744 000000ccec6fc7e0 : UnityOpenXR!DiagnosticReport_StartReport+0x1fc8
000000ccec6fc930 00007ffea3d7dbf4 : 000000ccec6fc9b0 00007ffea3d7dbf4 fffffffffffffffe 0000000000000000 : UnityOpenXR!DiagnosticReport_StartReport+0x108c
000000ccec6fc9b0 00007ffea3d7dd04 : 000000ccec6fcfd0 00007ffea3d7dd04 0000000000000001 3f80000000000000 : UnityPlayer!UnityXRDisplayGraphicsThreadProvider_5::Adapt_PopulateNextFrameDesc+0x10c
000000ccec6fcfd0 00007ffea3d7de8c : 000000ccec6fd5e0 00007ffea3d7de8c 0000000000000001 3f80000000000000 : UnityPlayer!UnityXRDisplayGraphicsThreadProvider_7::Adapt_PopulateNextFrameDesc+0x9c
000000ccec6fd5e0 00007ffea3d791b0 : 000000ccec6fdc00 00007ffea3d791b0 0000000000000001 3f80000000000000 : UnityPlayer!UnityXRDisplayGraphicsThreadProvider_8::Adapt_PopulateNextFrameDesc+0xf4
000000ccec6fdc00 00007ffea40dbc54 : 000000ccec6ff9d0 00007ffea40dbc54 0000000000000001 3f80000000000000 : UnityPlayer!XRDisplaySubsystem::GfxThread::FrameBoundary+0x198
000000ccec6fdc90 00007ffea40d6a58 : 00000263b0f91c60 0000000000000000 0000000000000001 0000000000000000 : UnityPlayer!GfxDeviceWorker::RunCommand+0x5124
000000ccec6ffa30 00007ffea40d69a8 : 000000ccec6ffa70 00007ffea40d69a8 00000263b029fc10 00000262a0054790 : UnityPlayer!GfxDeviceWorker::RunExt+0xa0
000000ccec6ffa70 00007ffea40d68dc : 000000ccec6ffaa0 00007ffea40d68dc 0000000000000960 0000026330002760 : UnityPlayer!GfxDeviceWorker::Run+0xc0
000000ccec6ffaa0 00007ffea3736564 : 000000ccec6ffab0 00007ffea3736564 000000ccec6ffb70 00007ffeca580258 : UnityPlayer!GfxDeviceWorker::RunGfxDeviceWorker+0xc
000000ccec6ffab0 00007ffeca580258 : 000000ccec6ffb70 00007ffeca580258 0000000000000001 0000026330002760 : UnityPlayer!Thread::RunThreadWrapper+0x154
000000ccec6ffb70 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x58

@AMollis
Copy link
Member

AMollis commented Mar 18, 2023

@Suddelnuppe, are you able to share a crash dump file?

Also, can you please provide the versions of the OpenXR Plugin and the Microsoft Mixed Reality OpenXR Plugin?

@Suddelnuppe
Copy link
Author

Hey @AMollis could you provide me with your work mail. I will gladly share what we have.

@AMollis AMollis added this to the MRTK 2.x future milestone Apr 17, 2023
@AMollis AMollis added the Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on label Jan 12, 2024
@IssueSyncBot
Copy link
Collaborator

Hi @Suddelnuppe,

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!

@IssueSyncBot IssueSyncBot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Feedback Request MRTK2 Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on
Projects
None yet
Development

No branches or pull requests

3 participants