New issue
Advanced search Search tips

Issue 766481 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Remove ServerSharedBitmapManager Usage in Content

Project Member Reported by jonr...@chromium.org, Sep 19 2017

Issue description

With the viz process to be split out, ServerSharedBitmapManager will no longer be in the same process as content.

Currently it is used directly in non-testing code:
  -  BrowserMainLoop::PostMainMessageLoopStart() for tracing
  -  GpuProcessTransportFactory::EstablishedGpuChannel
  -  RenderProcessHostImpl to access viz::SharedBitmapAllocationNotifierImpl
  -  RenderWidgetHostImpl::OnShowDisambiguationPopup to grab a SharedBitmap

These need to be updated to work with just a SharedBitmapManager object. Which will be backed by the process' ClientSharedBitmapManager, but that will be hidden away.

While we are at is, we should remove the singleton nature of ServerSharedBitmapManager
 

Comment 1 by laforge@google.com, Nov 8 2017

Components: -Internals>Viz Internals>Services>Viz
Migrating from Internals>Viz to Internals>Services>Viz.
Status: Assigned (was: Untriaged)
Cc: -mustash-bugs@google.com jonr...@chromium.org sadrul@chromium.org kylec...@chromium.org samans@chromium.org
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment