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

Issue metadata

Status: Archived
Last visit > 30 days ago
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Sign in to add a comment

Use single shared memory segment for sharing field trials

Reported by, Oct 7 2016 Back to list

Issue description

Currently, we create a new shared memory segment per process host (it gets stored in RenderProcessHostImpl or GpuProcessHost). Let's hoist that variable up into a static base::FieldTrialList member, and also start using the PersistentMemoryAllocator to store all the field trials instead of using a string.
Project Member

Comment 1 by, Oct 25 2016

The following revision refers to this bug:

commit 0b496492defaf5f2f70e08318c36568ccce9ce87
Author: lawrencewu <>
Date: Tue Oct 25 16:28:14 2016

Use SharedPersistentMemoryAllocator to share field trial state

Change the method by which we share field trial state from using a
SharedMemory class to SharedPersistentMemoryAllocator. Adds this
allocator to the base::FieldTrialList singleton, so there is only one copy
of this state on the browser process vs. a copy for each process host
which is how it currently works (from

BUG= 653874 

Cr-Commit-Position: refs/heads/master@{#427378}


Status: Fixed (was: Assigned)

Comment 3 by, Jan 21 2017

Labels: VerifyIn-57

Comment 4 by, Mar 4 2017

Labels: VerifyIn-58

Comment 5 by, Apr 17 2017

Labels: VerifyIn-59

Comment 6 by, May 30 2017

Labels: VerifyIn-60

Comment 7 by, Aug 1 2017

Labels: VerifyIn-61

Comment 8 by, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment