New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 804955 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Feature

Blocking:
issue 795291



Sign in to add a comment

Use separate shared memory for different sensors

Project Member Reported by juncai@chromium.org, Jan 23 2018

Issue description

Currently the generic sensor code initializes a chunk of shared memory and use it for different sensors. It would be better to initialize separate shared memory for different sensors. This makes sense for the sensor permission request since allowing one sensor won't automatically expose the shared memory that is used for all sensor types.
 
Cc: mattcary@chromium.org
Blocking: 795291
Cc: alexilin@chromium.org
If using many shared buffers is inefficient then an alternative is dividing up sensors based on the level of permission required.

Sign in to add a comment