Constant RUNTIMEIPC entries being logged - Quest 2 v67.0.0.648.356

[nexusmtz]

When the headset is on (not in standby), RUNTIMEIPC entries are being logged at a rate of about 230 per second. The warnings/info are a loop of the following:

07-14 19:44:57.320 8059 8256 W REFLECT [RUNTIMEIPC]: ipc_GetServerState FAILED: PtDistPrioState
07-14 19:44:57.320 8059 8256 I RuntimeIPCClient [RUNTIMEIPC]: Shutdown: 2, Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.320 8059 8256 I RuntimeIPCClient [RUNTIMEIPC]: ReleaseRef: Remaining refs: 1, Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 I RuntimeIPCClient [RUNTIMEIPC]: ConnectToServer: SUCCESS: Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 1106 1533 W RPCServer [RUNTIMEIPC]: GetServerStateEntry: Shared memory for PtDistPrioState is invalid. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059:, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: GetServerStateMemoryId: Failed to find entry in server for PtDistPrioState. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: ClientCallWithRetries (GetServerStateMemoryId): Trying again, attempt 2 of 3, Client: Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 1106 1533 W RPCServer [RUNTIMEIPC]: GetServerStateEntry: Shared memory for PtDistPrioState is invalid. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059:, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: GetServerStateMemoryId: Failed to find entry in server for PtDistPrioState. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: ClientCallWithRetries (GetServerStateMemoryId): Trying again, attempt 3 of 3, Client: Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 1106 1533 W RPCServer [RUNTIMEIPC]: GetServerStateEntry: Shared memory for PtDistPrioState is invalid. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059:, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: GetServerStateMemoryId: Failed to find entry in server for PtDistPrioState. Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)
07-14 19:44:57.375 8059 8256 W RuntimeIPCClient [RUNTIMEIPC]: ClientCallWithRetries (GetServerStateMemoryId): Failed after 3 attempts, Client: Client: com.oculus.systemdriver:com.oculus.vrruntimeservice:8059, Server: native_process.system:/system/bin/mrsystemservice (MrSystemServiceIPCServer)

This is causing unnecessary processing and is contributing to heat and power draw. The entries are present immediately after a factory reset and persist while the headset is active. When the headset is in standby, the RUNTIMEIPC logging subsides and typical log pacing resumes.

Headset info:

Quest 2
releases-oculus-12.0-v67
hollywood-user 12 SQ3A.220605.009.A1 51062550068500150 release-keys
67.0.0.648.356.621284304 (Version)
67.0.0.651.358.621285396 (Runtime Version)

[MetaQuestSupport]

Hey there, @nexusmtz. We were in the area and just so happened to see that you are having some issues with your headset. We'd be happy to offer some assistance. Firstly, we would like for you to answer some questions so we can get a better understanding of what's happening.

1. Is this issue with heat and battery drain only happening while using your Quest 2 on PVCR, or does this also occur in standalone mode?
2. Have you tried any troubleshooting to try to fix this?
3. Has your ability to play your Quest 2 diminished, and about by how long?
4. Are you playing with the headset while it is attempting to charge?
5. Does your headset take longer than 2 hours to get to full charge?

We hope to hear from you soon!

[MetaQuestSupport]

Hey again, @nexusmtz! We wanted to swing back around and check if you're still having issues with this or have any additional questions. Please let us know! we're happy to help!

[nexusmtz]

1. This happens in standalone and continues during Link / Air Link.
2. It persists after reboot, power off/on, factory reset, wi-fi on or off, USB connected or not.
3. Unable to quantify the effect. Since the events are happening continuously while active, there is no isolated point of reference.
4. No. However, in testing, the issue does persist while charging.
5. If depleted below 10%, the headset (in standby) does seem to take more than 2 hours on the standard 10W charger, but I have not timed it.

What is causing the flood of messages, and how do I stop them?

[MetaQuestSupport]

Thank you for sharing those answers with us. Now that we have these details, we think the best course of action would be to have you submit a bug report for this issue. You can find the steps to do so by following this link here. Please keep in mind that when you submit a report, information about your device, account, and the apps you're currently running will be automatically included in this report. You're also able to choose to include complete logs and diagnostics, such as user activity logs, network logs, and crash reports associated with your device. These may contain details that help us better understand and fix issues. We appreciate you bringing this issue to us, and we hope to have a fix for this issue very soon.

[MetaQuestSupport]

Hi @nexusmtz, we trust you are well! Just checking back with you to see if you were able to submit the report? 

Please let us know if you have any issues! 

[nexusmtz]

Yes, I submitted the report. However, there is no feedback or tracking, so I have no idea what is happening to resolve the issue.

I also have no way to re-join the Quest 2 PTC to see if it has been resolved in a pre-release version as I could do before the factory reset.

[MetaQuestSupport]

Thank you for submitting the bug report, @nexusmtz. We also recommend you check in on our V68 PTC Thread to see if anyone else is having the same issues. Any details you can provide there on how to check would be helpful for anyone else to confirm the issues are present for them as well. In the meantime, let us know if you have any further questions, or issues you want assistance with.

[byte_lab]

I'm having the same issue.

[MetaQuestSupport]

Hello, @byte_lab! We definitely want to help get your headset back on track as well, so we'd love to assist further with the your headset's entries. In order for us to get a better idea of the specifics of your particular situation to begin with, please clarify the following points when you get a chance and we can continue from there: 
 

• Is this issue with heat and battery drain only happening while using your Quest 2 on PVCR, or does this also occur in standalone mode?
• Has your ability to play your Quest 2 diminished, and about by how long? Are you able to enter the home environment, as well as launch a game? 
• Are you playing with the headset while it is attempting to charge?
• Does your headset take longer than 2 hours to get to full charge
• So we don't repeat any, what troubleshooting steps have you already tried?