Closed Bug 1635197 Opened 6 years ago Closed 6 years ago

Content process stays with PROCESS_PRIORITY_BACKGROUND after App restart on Oculus Quest

Categories

(GeckoView Graveyard :: Sandboxing, defect)

Product:
GeckoView Graveyard
Component:
Sandboxing
Platform:
Unspecified
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1635914

People

(Reporter: mortimergoro, Unassigned)

Details

STR:

  • Open Firefox Reality (make sure it was killed before)
  • Tab0 content process has FOREGROUND PRIORITY (-10)
  • Click the Oculus menu button and exit the application
  • Tab0 content process sets BACKGROUND priority
  • Reopen Firefox Reality
  • Tab0 content process keeps BACKGROUND priority. WebXR performance is impacted
  • If you force onPAuse/onResume (just dimming the screen) the Tab0 content process get's the correct FOREGROUND PRIORITY

It seems that SetDocShellIsActive is not called after a onDestroy/onCreate app life cycle on Quest. It gets correctly called after onPause/onResume.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

Moving content process management bugs to the new GeckoView::Sandboxing component.

Component: General → Sandboxing
Product: GeckoView → GeckoView Graveyard
You need to log in before you can comment on or make changes to this bug.