Issue metadata
Sign in to add a comment
|
force-mediafoundation does not work anymore
Reported by
alaoui....@gmail.com,
Oct 24 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Add the flag --force-mediafoundation to the chrome shortcut 2. Run chrome and go to https://simpl.info/imagecapture/ 3. The video from the camera appears 4. In a new tab, go to chrome://media-internals/ -> Video Capture What is the expected behavior? The capture should be using MediaFoundation What went wrong? The capture is using Direct Show Did this work before? Yes 59 Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: stable OS Version: 10 Flash Version: Could be related to the introduction of a separate "video capture service" process. Maybe, this new process does not start with the flags passed to the main process.
,
Oct 24 2017
re report: I think your hunch is right. Looks like the command-line flag does not get forwarded to the video capture service. Can you please confirm by disabling the video capture service using --disable-features=MojoVideoCapture?
,
Oct 24 2017
It works by using --single-process. I will try with --disable-features=MojoVideoCapture.
,
Oct 24 2017
Just tested, it works by using --disable-features=MojoVideoCapture.
,
Oct 24 2017
,
Oct 24 2017
CL for fix is up for review: https://chromium-review.googlesource.com/c/chromium/src/+/735528
,
Oct 24 2017
chfremer@, Thank you for the fix. Please make sure to merge into respective milestones (M62 & 63?) once the fix has been landed in trunk.
,
Oct 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4606621f1faf77ae8ba074ae3b2a343270fd883e commit 4606621f1faf77ae8ba074ae3b2a343270fd883e Author: Christian Fremerey <chfremer@chromium.org> Date: Wed Oct 25 21:17:58 2017 Propagate flag kForceMediaFoundationVideoCapture to video capture service Because the flag was not propagated, it stopped working with the rollout of the video capture service in M61. As a workaround until the fix reaches stable, users can disable the video capture service using command-line flag --disable-features=MojoVideoCapture. Bug: 777880 Change-Id: I0971d0578893f80c7706373812ee3888d9029f8e Reviewed-on: https://chromium-review.googlesource.com/735528 Reviewed-by: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Christian Fremerey <chfremer@chromium.org> Cr-Commit-Position: refs/heads/master@{#511593} [modify] https://crrev.com/4606621f1faf77ae8ba074ae3b2a343270fd883e/content/browser/utility_process_host_impl.cc
,
Dec 7 2017
Sorry for the delay. The fix has landed in 64. Since this flag was a developer-only feature and there is a workaround described in #4, I feel that a merge into 63 is not needed. With 63 having reached stable, a merge into 62 should also no longer be needed. Please feel free to reopen if you disagree. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mcasas@chromium.org
, Oct 24 2017Components: Blink>GetUserMedia Blink>MediaStream
Status: Available (was: Unconfirmed)