New tests in content_browsertests, WebContentsVideoCaptureDeviceBrowserTest.* fail to run on the Linux bots in the waterfall. The root cause seems to be that when these tests are run in a particular way(*), the shared memory pool being managed by viz::InterprocessFramePool encounters OS failures around an unlink() call in shared_memory_helper.cc:
https://cs.chromium.org/chromium/src/base/memory/shared_memory_helper.cc?rcl=1c6d493beeda1b183a95c41598160f6ff51fbaf3&l=22
(*) The particular way being that:
1. Tests are being run in-parallel, rather than single-process mode.
2. The extra --enable-features=VizDisplayCompositor command line flag is being used, which means the shmem pool exists in the GPU process instead of the browser process.
Note that the regular content_browsertests run does not have any issues (the shmem pool exists in the browser process instad).
Example failure logs (from https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29%2832%29/47651):
[17267:17294:0126/232827.150906:WARNING:shared_memory_helper.cc(23)] unlink: Operation not permitted (1)
[17267:17294:0126/232827.151470:ERROR:video_capture_buffer_pool_impl.cc(231)] Error initializing VideoCaptureBufferTracker
Comment 1 by m...@chromium.org
, Jan 29 2018