cancel
Showing results for 
Search instead for 
Did you mean: 

"capture could not open mutex: The system cannot find the file specified." (Quest 2 Link)

BIIIIIIIIIIIIIRD
Explorer

Is anyone else being spammed with "[xrstreaming] OculusVadSharedMemoryProducer::initialize: capture could not open mutex: The system cannot find the file specified." in their logs?

I'm getting it exactly every other second:

03/07 08:05:38.470 {DEBUG} [xrstreaming] OculusVadSharedMemoryProducer::initialize: capture could not open mutex: The system cannot find the file specified.
03/07 08:05:38.489 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1350525728024 (received at 30984199223700), offset divergence 37323
03/07 08:05:38.602 {DEBUG} [xrstreaming] receive pong: org 30984310517400 recv 1350637311357 xmt 1350638308128 (received at 30984311806900), offset divergence 37323
03/07 08:05:38.602 {DEBUG} [xrstreaming] new clock offset=-29633673394689 (rtt: 207929, dispersion: 58737, jitter: 91214)
03/07 08:05:38.686 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:39.489 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1351525867242 (received at 30985199359700), offset divergence 37323
03/07 08:05:39.603 {DEBUG} [xrstreaming] receive pong: org 30985313068200 recv 1351639803961 xmt 1351639940628 (received at 30985313455100), offset divergence 26442
03/07 08:05:39.603 {DEBUG} [xrstreaming] new clock offset=-29633673389355 (rtt: 250233, dispersion: 44489, jitter: 91547)
03/07 08:05:40.236 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:40.470 {DEBUG} [xrstreaming] OculusVadSharedMemoryProducer::initialize: capture could not open mutex: The system cannot find the file specified.
03/07 08:05:40.476 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:40.490 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1352526238648 (received at 30986199717600), offset divergence 31776
03/07 08:05:40.607 {DEBUG} [xrstreaming] receive pong: org 30986315698900 recv 1352643063232 xmt 1352644088909 (received at 30986317575700), offset divergence 31776
03/07 08:05:40.607 {DEBUG} [xrstreaming] new clock offset=-29633673389355 (rtt: 250233, dispersion: 74612, jitter: 108847)
03/07 08:05:40.876 {DEBUG} [VirtualDisplay] System overlay reported as not present but window capture system is following 1 windows
03/07 08:05:41.491 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1353527828960 (received at 30987201353100), offset divergence 31776
03/07 08:05:41.556 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:41.609 {DEBUG} [xrstreaming] receive pong: org 30987315779400 recv 1353642531512 xmt 1353645694169 (received at 30987319190300), offset divergence 31776
03/07 08:05:41.609 {DEBUG} [xrstreaming] new clock offset=-29633673372009 (rtt: 248243, dispersion: 52429, jitter: 115101)
03/07 08:05:42.026 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:42.347 {INFO} [xrstreaming] RemoteMic: NetworkMetrics: [0.120,54.175]9.871
03/07 08:05:42.471 {DEBUG} [xrstreaming] OculusVadSharedMemoryProducer::initialize: capture could not open mutex: The system cannot find the file specified.
03/07 08:05:42.491 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1354527937554 (received at 30988201408800), offset divergence 49122
03/07 08:05:42.546 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:42.609 {DEBUG} [xrstreaming] receive pong: org 30988316545400 recv 1354643312814 xmt 1354645998439 (received at 30988319472100), offset divergence 32080
03/07 08:05:42.609 {DEBUG} [xrstreaming] new clock offset=-29633673353123 (rtt: 241075, dispersion: 41316, jitter: 123082)
03/07 08:05:43.426 {INFO} [xrstreaming] RemoteHeadphones: IPCMetrics: [7.484,12.711]9.874
03/07 08:05:43.493 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 1355529279428 (received at 30989202744900), offset divergence 50966
03/07 08:05:43.556 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:43.609 {DEBUG} [xrstreaming] receive pong: org 30989316712000 recv 1355643468803 xmt 1355646222501 (received at 30989319687300), offset divergence 50966
03/07 08:05:43.609 {DEBUG} [xrstreaming] new clock offset=-29633673353998 (rtt: 221602, dispersion: 35758, jitter: 118836)
03/07 08:05:43.766 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:43.866 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:44.406 {INFO} [xrstreaming] OculusVadSharedMemoryConsumer::read: no data available
03/07 08:05:44.471 {DEBUG} [xrstreaming] OculusVadSharedMemoryProducer::initialize: capture could not open mutex: The system cannot find the file specified.
11 REPLIES 11

TexasRanger730c
Honored Guest

I am having the same problem.  Looks like you never got answer?

 

MetaQuestSupport
Community Manager
Community Manager

Hi @TexasRanger730c. We see that you could not open up mutex and that you were not able to find your file. That is not the experience that we want our users to have, but do not stress; we will help you straighten this out. Go ahead and follow the link here to our amazing support team. They will gladly lend a hand further with this pesky issue via live chat, email, or a callback. Hope this was helpful!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

Nothing, contacting support didn't help either

We went through a complete clean wipe of Oculus on my computer to try and get rid of it.  It came right back after a few minutes.  And there are three versions of oculusClient.exe running at the same time.  The Oculus app went in to a hard lock up as well.  We are still working through it.

I ended up ignoring it. Thought it was causing performance issues but it ended up being something else. What issues are you having?

TexasRanger730c
Honored Guest

I was having some stuttering, but like you I don't think this bug is the culprit.  You may have the right plan, just ignore it.

 

I was using a 1070 at the time and running the headset at 2700xSomething @120hz, but for some reason it was still encoding everything at 3600xWhatever. Manually lowering the resolution width in the debug tool fixed the stuttering for me, might not be of much help to you though

Im getting this error. help pls

hmza.hassan.2024
Honored Guest

I have also the same issue.

Get Help
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset
Tips and Tricks: Help with Pairing your Meta Quest
Trouble With Facebook/Instagram Accounts?