Make media::InitMediaLibrary work with the sandbox
Initializing the media library entails getting information about the CPU for the libyuv and ffmep libraries. Retrieving that information might access the file system (/cpu/procinfo). The extension handler code would initialize the media library before the sandbox is turned on. As part of the effort to move process launching to the service manager where the service process is always sandboxed, this CL adds a new InitializeMediaLibraryInSandbox method that lets callers specify the CPU info so the initialization can be done inside the sandbox. The client library of the media gallery util service which was the reason why extension handlers would need to initialize the media library, now do it explicitly and provide the CPU info. As a result, extension handlers related files can be removed. Bug: 823931 Change-Id: Ie1630f3ff04c94901224750ffdea4423bd1b3186 Reviewed-on: https://chromium-review.googlesource.com/966925Reviewed-by:Lei Zhang <thestig@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Jay Civelli <jcivelli@chromium.org> Cr-Commit-Position: refs/heads/master@{#549813}
Showing
Please register or sign in to comment