Closed Bug 956675 Opened 12 years ago Closed 8 years ago

Lazy load the binder thread pool in the content process

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: cyu, Unassigned)

Details

Ideally, content processes should not start the binder thread pool. Camera and video decoding are 2 exceptions, but not all apps need these capabilities. We may consider lazy loading the binder thread pool on demand.
AudioTrack also needs the binder thread pool. And the fist calling of android::ProcessState::self() in content process have to be called on main thread. See Bug 839007 Comment 26.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.