Skip to main content
New Participant
August 28, 2025

Game crashing on restart

  • August 28, 2025
  • 2 replies
  • 182 views

Hello. I'm developing a game for Quest 2 and 3 and have encountered issues with the game crashing on Quest 2. The weird thing is that only crashes on some of our quests, some of them work fine while others will start the game once then crash when trying to the start the game again. There are no noticeable differences between the Quest 2 headsets either. 

The source of the crash seems to be this error: MemoryBroker: INPUT_TYPE_MAP: client com.DefaultCompany.Game does not have access (app ops or VR focus). I have tried multiple solutions like forcing a clean shutdown and INPUT_TYPE_MAP permissions but none of them seem to work. 

I think it's likely related to the RAM use of the game but there is not much more I can to do optimize it further and shouldn't be needed either since it works normally on other headsets.

This topic has been closed for replies.

2 replies

VirtuallyARealDinosaur
Community Manager
September 8, 2025

Hello!

Can you create a adb bugreport and provide it to me over PM?

Thanks!

 

RiverExplorer
Honored Contributor
September 8, 2025

Sounds like it might be a timing issue.

One thing I misunderstood when I started writing with Unity is the Awake() and Start() methods.

Start() *CAN* start before Awake() finishes. Even within the same component. When Awake() is async and has an await (even indirectly). I called a method in Awake() that called another method that did an await.  Boom, mucked up timing problem.

The docs say that Awake() is called before Start(). It does NOT say that Start() is only called after Awake() finishes. And it does NOT say that Start() is called only when all Awake() calls have finished.

Now add the complexity of one components Start() depending on another components   Awake() to have set up things.

Then add OnEnable() ... same issues.

 

 

 

RiverExplorer.US]@gmail.com https://RiverExplorer.games