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

Issue 798221 link

Starred by 4 users
Status: Available
Owner: ----
Cc:
█ dvallet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Enable memfd_create implementation of SharedMemory in OS_LINUX

Project Member Reported by dvallet@chromium.org, Jan 1 2018 
Reland
https://chromium-review.googlesource.com/c/chromium/src/+/809014

so we can use memfd_create instead of a tmp anonymous file for shared memory. This would allow headless running in instances that don't have space on /dev/shm by default. 

For this to happen, use of SharedMemory needs to be refactored so that  SharedMemory::GetReadOnlyHandle is only called once all the data has been written to shared instance, and SEAL_WRITE can be safely applied.

What is the expected result?


What happens instead of that?


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Project Member

Comment 1 by sheriffbot@chromium.org, Jan 2

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by thomasanderson@chromium.org, Jan 2

Status: Available (was: Untriaged)
►

Sign in to add a comment