| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, they were being put in assets/cast_shell_apk/, which was
not correct, as v8_initializer.cc (since
https://codereview.chromium.org/1400953002) expects these assets to
appear directly in the assets/ folder. As a result, the Cast shell
would crash while initializing on Android TV.
BUG=540788
Review URL: https://codereview.chromium.org/1741773003
Cr-Commit-Position: refs/heads/master@{#378062}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
by default.
This CL moves background color from WebView to WebFrameWidget,
which allows for setting the background color independently per
local root. WebViewImpl still implements background color for
the main frame, but it now goes through a WebViewFrameWidget
interface.
BUG=515625
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1565893004
Cr-Commit-Position: refs/heads/master@{#377937}
|
|
|
|
|
|
|
|
|
|
| |
This only applied to prefixed EME.
BUG=249976
Review URL: https://codereview.chromium.org/1737213002
Cr-Commit-Position: refs/heads/master@{#377917}
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/1740633002
Cr-Commit-Position: refs/heads/master@{#377540}
|
|
|
|
|
|
|
|
| |
Also add include header to satisfy CQ check
Review URL: https://codereview.chromium.org/1739463002
Cr-Commit-Position: refs/heads/master@{#377525}
|
|
|
|
|
|
|
|
|
|
| |
No longer needed (and in fact, no longer does anything).
BUG=internal b/24145290
Review URL: https://codereview.chromium.org/1738653002
Cr-Commit-Position: refs/heads/master@{#377514}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reduces the amount of resources that background work
can use by making the background thread that runs pre-paint
tasks use a priority that makes it run on a single small core
on big.LITTLE devices.
Threads used for foreground work are now given normal priority
on all platforms.
BUG=504515
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1616953003
Cr-Commit-Position: refs/heads/master@{#377490}
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/1726013002
Cr-Commit-Position: refs/heads/master@{#377134}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create only one CmaMediaPipelineClient, and reuse it for all
message filters.
BUG=None
TEST=Play media in cast_shell multiple times.
R=halliwell@chromium.org,yucliu@chromium.org
Review URL: https://codereview.chromium.org/1707113002
Cr-Commit-Position: refs/heads/master@{#376764}
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will straighten out a dependency issue created by the
public/internal boundary. Both public and internal targets can depend on
this target.
BUG=internal b/27254616
Review URL: https://codereview.chromium.org/1714083003
Cr-Commit-Position: refs/heads/master@{#376605}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL makes mojo media services highly configurable by
providing finer control on what service is enabled on which
platform. For example, on Android and Desktop, we want use the
default media Renderer but use the mojo CDM. On ChromeCast, we
want to use the mojo Renderer and the mojo CDM.
Tested with various gn argument combinations, e.g.
- mojo_media_host="utility", mojo_media_services=["cdm"]
Both clear and encrypted playback (Clear Key) work. In the
encrypted case, we use DecryptingDemuxerStream and
MojoDecryptor to do decrypt-only.
- mojo_media_host="utility", mojo_media_services=["renderer"]
Clear playback works using remote renderer. Encrypted playback
doesn't work because a remote renderer doesn't support a local
CDM.
- mojo_media_host="gpu", mojo_media_services=["renderer", "cdm"]
Both clear and encrypted playback work. In both cases a remote
renderer is used. In the encrytped case, the remote renderer
uses a remote CDM in the GPU process.
BUG=571247
TEST=See above.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
Review URL: https://codereview.chromium.org/1712033002
Cr-Commit-Position: refs/heads/master@{#376498}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following android's documentation, native apps can set a referrer with
the format android-app://com.foo.bar. This is supported by the Java
side, but not the native code.
TBR=alokp@chromium.org,asargent@chromium.org # Adding a parameter in chromecast/ and extensions/
TESTED=adb shell am start -n com.google.android.apps.chrome/.Main -a "android.intent.action.VIEW" -d 'http://www.whatismyreferer.com/' --eu "android.intent.extra.REFERRER" "android-app://com.foo.bar"
BUG=537863
Review URL: https://codereview.chromium.org/1416863004
Cr-Commit-Position: refs/heads/master@{#376423}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The user gesture information was required by the permission bubble code. With bug 545476
fixed, this is no longer needed.
This CL is the second CL in a suite of three CL that remove the passing of the user gesture
information from the renderer process content layer to the browser process chrome layer:
1. https://codereview.chromium.org/1695943002
2. <this>
3. https://codereview.chromium.org/1696883004
BUG=423770
TBR=wez@chromium.org (blimp/ trivial changes)
Review URL: https://codereview.chromium.org/1695953002
Cr-Commit-Position: refs/heads/master@{#376420}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also moves the workaround for crbug.com/144683 from CmaRenderer
to MediaPipelineImpl so that it can be shared by both CMA and
mojo media pipeline.
BUG=571155
Review URL: https://codereview.chromium.org/1709823002
Cr-Commit-Position: refs/heads/master@{#376334}
|
|
|
|
|
|
|
|
|
|
| |
With this patch, audio pipeline is working when cast_shell is compiled with GN flag: enable_mojo_media="browser".
BUG=571155
Review URL: https://codereview.chromium.org/1670763003
Cr-Commit-Position: refs/heads/master@{#376293}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Rename DefaultMojoMediaClient to TestMojoMediaClient.
- Add a new stub DefaultMojoMediaClient, which will be used by Chromium for
non-Android platforms.
- Add gn variable enable_test_mojo_media_client to enable TestMojoMediaClient
for Chromium builds. This can be used for local tests.
- Separate MojoMediaApplication from it's creation so that it's easier to create
MojoMediaApplication with a customized MojoMediaClient.
- Add CreateMojoMediaApplication() to create the app with default MojoMediaClient.
- App tests will always use TestMojoMediaClient.
- Update BUILD.gn to support all above.
BUG=570357
TEST=Tests still work. Tried enable_test_mojo_media_client locally.
Review URL: https://codereview.chromium.org/1702803002
Cr-Commit-Position: refs/heads/master@{#376193}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts https://codereview.chromium.org/1477483003/ which was
intended to fix a problem where media playback in browser tests
triggers metrics events that DCHECK on invalid session ID.
Previous attempt set a dummy session ID, but this could mask bugs
if we ever failed to set session ID correctly. Instead, explicitly
only set the dummy ID for running browser tests.
BUG=
Review URL: https://codereview.chromium.org/1510973007
Cr-Commit-Position: refs/heads/master@{#376099}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL enables SurfaceView fullscreen video with the unified media pipeline
in cases where we use the AVDA deferred rendering strategy today.
* There's a new media interface called SurfaceManager with two methods:
CreateFullscreenSurface() and NaturalSizeChanged().
* SurfaceManager is implemented by RendererSurfaceViewManager, which is a
RenderFrameObserver, and BrowserSurfaceViewManager, which is created for
each RenderFrame by MediaWebContentsObserverAndroid.
* BrowserSurfaceViewManager creates a ContentVideoView in response to a
CreateFullscreenSurface message, and registers it in a surface map that the
decoder can look up in the GPU process.
* WMPI interacts with SurfaceManager on behalf of the decoder. It passes
GpuVideoDecoder a callback for requesting surfaces which it calls before
initializing VDAs.
* In response to the callback, if the player is in fullscreen WMPI will pass
the request to the SurfaceManager which will return the surface id to GVD. If
the player is not in fullscreen WMPI will return a null surface id.
* When GVD gets a surface id back it completes its initialization by calling
VDA::Initialize with the surface id and the VDA will render to the given
surface.
* WMPI records that it got a surface request callback so that it knows that
future fullscreen transitions will require a restart of the decoder in order
to switch surfaces.
* A future CL will allow us to switch the surface dynamically without
requiring a restart.
BUG=533630
Review URL: https://codereview.chromium.org/1655083002
Cr-Commit-Position: refs/heads/master@{#376068}
|
|
|
|
|
|
|
|
| |
BUG= internal b/27226258
Review URL: https://codereview.chromium.org/1711563002
Cr-Commit-Position: refs/heads/master@{#376056}
|
|
|
|
|
|
|
|
|
|
|
|
| |
* kCodecPCM_S16BE is actually optional.
* DTS will not be supported.
* Fix up config conversions for AC3/EAC3.
BUG= internal b/27218625
Review URL: https://codereview.chromium.org/1710463002
Cr-Commit-Position: refs/heads/master@{#375951}
|
|
|
|
|
|
|
|
|
|
|
| |
* AccessTokenSet to AccessTokenMap (it is a map!)
* LoadAccessTokensCallbackType to LoadAccessTokensCallback
TBR=alokp,torne
Review URL: https://codereview.chromium.org/1705433002
Cr-Commit-Position: refs/heads/master@{#375937}
|
|
|
|
|
|
|
|
|
|
|
| |
Some of the messages logged by ALSA backend are clearly warnings that
still allow playback to start, so let's adjust their log levels.
R=halliwell,jyw
Review URL: https://codereview.chromium.org/1699383002
Cr-Commit-Position: refs/heads/master@{#375764}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MediaPipeline[Impl/Proxy] now takes a base::Closure instead of
media::PipelineStatusCB. This is an improvement becuase:
1. It consolidates error reporting into MediaPipelineClient::error_cb.
2. Makes it consistent with media::Renderer::Flush interface, which
is being implemented using MediaPipelineImpl here:
https://codereview.chromium.org/1670763003/
BUG=571155
Review URL: https://codereview.chromium.org/1680983002
Cr-Commit-Position: refs/heads/master@{#375727}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
id:260001 of https://codereview.chromium.org/1702453002/ )
Reason for revert:
Unrelated to https://crbug.com/586902. Relanding.
Original issue's description:
> Revert of Reland "media: Refactor MojoMediaClient" with fix. (patchset #2 id:20001 of https://codereview.chromium.org/1690213002/ )
>
> Reason for revert:
> Suspected to break a layout test on android.
> https://crbug.com/586902
>
> Original issue's description:
> > Reland "media: Refactor MojoMediaClient" with fix.
> >
> > This reverts commit 29775799918ebeb0f2aedd554722e3db0c6211c2.
> >
> > Instead of specifying a platform based MojoMediaClient at compile time,
> > provide the capability of setting one at run time. This improves the flexibility
> > of using MojoMediaApplication in different cases. For example, on desktop, we
> > may want to run the MojoMediaApplication in the utility process (for the CDM
> > service) and in the GPU process (for hardware decoding). In those two cases,
> > we'll want to specify two different MojoMediaClients even though we are on the
> > same platform.
> >
> > TBR=alokp@chromium.org
> > BUG=570357,571155
>
> TBR=alokp@chromium.org,jam@chromium.org,thakis@chromium.org,xhwang@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=586902,570357,571155
TBR=alokp@chromium.org,jam@chromium.org,thakis@chromium.org,xhwang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=586902,570357,571155
Review URL: https://codereview.chromium.org/1697233002
Cr-Commit-Position: refs/heads/master@{#375491}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
id:20001 of https://codereview.chromium.org/1690213002/ )
Reason for revert:
Suspected to break a layout test on android.
https://crbug.com/586902
Original issue's description:
> Reland "media: Refactor MojoMediaClient" with fix.
>
> This reverts commit 29775799918ebeb0f2aedd554722e3db0c6211c2.
>
> Instead of specifying a platform based MojoMediaClient at compile time,
> provide the capability of setting one at run time. This improves the flexibility
> of using MojoMediaApplication in different cases. For example, on desktop, we
> may want to run the MojoMediaApplication in the utility process (for the CDM
> service) and in the GPU process (for hardware decoding). In those two cases,
> we'll want to specify two different MojoMediaClients even though we are on the
> same platform.
>
> TBR=alokp@chromium.org
> BUG=570357,571155
TBR=alokp@chromium.org,jam@chromium.org,thakis@chromium.org,xhwang@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=586902,570357,571155
Review URL: https://codereview.chromium.org/1702453002
Cr-Commit-Position: refs/heads/master@{#375482}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 29775799918ebeb0f2aedd554722e3db0c6211c2.
Instead of specifying a platform based MojoMediaClient at compile time,
provide the capability of setting one at run time. This improves the flexibility
of using MojoMediaApplication in different cases. For example, on desktop, we
may want to run the MojoMediaApplication in the utility process (for the CDM
service) and in the GPU process (for hardware decoding). In those two cases,
we'll want to specify two different MojoMediaClients even though we are on the
same platform.
TBR=alokp@chromium.org
BUG=570357,571155
Review URL: https://codereview.chromium.org/1690213002
Cr-Commit-Position: refs/heads/master@{#375352}
|
|
|
|
|
|
|
|
|
|
| |
Since b/21737919 has been fixed, these can be re-enabled.
BUG=
Review URL: https://codereview.chromium.org/1693783004
Cr-Commit-Position: refs/heads/master@{#375320}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some backends don't support additional effects streams, so separate
tests with effects streams out so that we can disable them on those
platforms. Also fix an issue in the AudioEffectsBackendStates test
where the config was never set.
BUG=
Review URL: https://codereview.chromium.org/1688373003
Cr-Commit-Position: refs/heads/master@{#375213}
|
|
|
|
|
|
|
|
| |
BUG=internal b/26972581
Review URL: https://codereview.chromium.org/1692073002
Cr-Commit-Position: refs/heads/master@{#375094}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://codereview.chromium.org/1688123002/ )
Reason for revert:
Breaks component build of mojo_media_client in gn builds on Windows.
Original issue's description:
> media: Refactor MojoMediaClient.
>
> Instead of specifying a platform based MojoMediaClient at compile time,
> provide the capability of setting one at run time. This improves the flexibility
> of using MojoMediaApplication in different cases. For example, on desktop, we
> may want to run the MojoMediaApplication in the utility process (for the CDM
> service) and in the GPU process (for hardware decoding). In those two cases,
> we'll want to specify two different MojoMediaClients even though we are on the
> same platform.
>
> BUG=570357,571155
TBR=alokp@chromium.org,jam@chromium.org,xhwang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=570357,571155
Review URL: https://codereview.chromium.org/1696613002
Cr-Commit-Position: refs/heads/master@{#375090}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of specifying a platform based MojoMediaClient at compile time,
provide the capability of setting one at run time. This improves the flexibility
of using MojoMediaApplication in different cases. For example, on desktop, we
may want to run the MojoMediaApplication in the utility process (for the CDM
service) and in the GPU process (for hardware decoding). In those two cases,
we'll want to specify two different MojoMediaClients even though we are on the
same platform.
BUG=570357,571155
Review URL: https://codereview.chromium.org/1688123002
Cr-Commit-Position: refs/heads/master@{#375037}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only OS_LINUX (see src/build/build_config.h) can rely on gl_renderer,
gl_vendor and gl_version to decide if it can start the GPU Process
based on the black list kSoftwareRenderingListJson.
Indeed GLStringManager::Initialize() is only effective #if defined(OS_LINUX).
On other platforms the triplet (os version, vendor id, device id) is enough
to make this decision.
Currently when using Mesa softpipe gl driver, chrome starts the gpu process
whereas it should not because GPU_FEATURE_TYPE_GPU_COMPOSITING is black
listed by default and because kGpuDriverBugListJson does not have any exception
for this driver.
The root cause is that gl_string_manager()->Initialize() is called after
starting the gpu process. Indeed it is called from PreMainMessageLoopRun
whereas the gpu process is started from BrowserThreadsStarted. See
BrowserMainLoop::CreateStartupTasks().
It is important to call gl_string_manager()->Initialize() before
starting the gpu process because it internally configures the gpu black list
using kGpuDriverBugListJson.
Unfortunatelly it is not as simple as moving gl_string_manager->Initialize
from ChromeBrowserMainParts::PreMainMessageLoopRun to PreCreateThreads. Indeed
GpuDataManagerImpl::GetInstance()->Initialize() is called at the end of
BrowserMainLoop::PreCreateThreads(), i.e. after parts_->PreCreateThreads().
And according to some comments around, it has to be after.
A solution would have been to add a new hook PreCreateThreadsEnd(). Since
it would have required to change content/public API. And it is not worth it
just to solve this bug. So the selected solution was to allow calling
GpuDataManager::SetGLStrings before Initialize.
Also:
- Added commandd line switches "gpu-no-complete-info-collection",
"gpu-testing-os-version", "gpu-testing-vendor-id", "gpu-testing-device-id",
"gpu-testing-gl-vendor", "gpu-testing-gl-renderer", "gpu-testing-gl-version".
- Renamed GpuBenchmarking::HasGpuProcess() to GpuBenchmarking::HasGpuChannel().
Which return true if a channel exists between renderer process and gpu process.
- Re-implemented GpuBenchmarking::HasGpuProcess by sending a new sync IPC
GpuHostMsg_HasGpuProcess that replies true if a gpu process exists. Even if
the channel between browser process and gpu process is still establishing.
- Uses of the new GpuBenchmarking::HasGpuChannel in gpu_process.py instead of
previous GpuBenchmarking::HasGpuProcess.
- Added GpuProcess.no_gpu_process unit test to gpu_process_tests.py.
- Added GpuProcess.software_gpu_process unit test to gpu_process_tests.py.
- Added GpuDataManagerImplPrivateTest_SetGLStringsDefered to content_unittests.
BUG=571895
R=jam@chromium.org, kbr@chromium.org, tsepez@chromium.org, zmo@chromium.org
TEST= GALLIUM_DRIVER=softpipe LIBGL_ALWAYS_SOFTWARE=1 chrome
CHROME_DEVEL_SANDBOX=out/Release/chrome_sandbox ./content/test/gpu/run_gpu_test.py gpu_process
CQ_INCLUDE_TRYBOTS=tryserver.chromium.win:win_optional_gpu_tests_rel
Review URL: https://codereview.chromium.org/1547793004
Cr-Commit-Position: refs/heads/master@{#374969}
|
|
|
|
|
|
|
|
| |
BUG=internal b/26163065
Review URL: https://codereview.chromium.org/1688093002
Cr-Commit-Position: refs/heads/master@{#374848}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RendererImpl and MediaSourceDelegate wait for CDM to be available to start initialization if any stream is encrypted. Since CDM is available, we can simply pass the CdmContext down and thus avoid the SetCdmReadyCB/CdmReadyCB/SetCdm round trip.
Also decoder initialization will not be associated with CdmAttachedCB any more. Instead, we'll only handle it in RendererImpl and MediaSourceDelegate based on the result of audio and video Renderer/Decoder/DecryptingDemuxerStream initialization.
This CL is part 1 where all decoders/renderers are fixed. In the next CL (part 2), DecryptingDemuxerStream and MediaSourceDelegate will be fixed.
TBR=alokp@chromium.org,bbudge@chromium.org
BUG=580250
TEST=Updated unittests.
Review URL: https://codereview.chromium.org/1666653002
Cr-Commit-Position: refs/heads/master@{#374835}
|
|
|
|
|
|
|
|
|
|
|
| |
All users are on the new EDK now. This wipes out third_party/mojo,
updates all dependencies, and removes the use-new-edk flag.
BUG=None
Review URL: https://codereview.chromium.org/1676913002
Cr-Commit-Position: refs/heads/master@{#374631}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Proprietary resources need to be packed into cast_shell.pak, so move
this packing step into internal build files. This has the added benefit
of reducing the number of entry points between internal and public code.
Bug: b/27104641
Test: diff <out>/cast_shell.pak <out>/cast_shell.pak.old is clean.
Related internal CL:
https://eureka-internal-review.git.corp.google.com/#/c/43773
BUG=None
Review URL: https://codereview.chromium.org/1686713003
Cr-Commit-Position: refs/heads/master@{#374564}
|
|
|
|
|
|
|
|
|
|
| |
Add slan@ and alokp@; remove gunsch@.
BUG=none
Review URL: https://codereview.chromium.org/1682023002
Cr-Commit-Position: refs/heads/master@{#374444}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All overrides just return nullptr.
A couple of gmock tests in resource_bundle_unittest.cc had references,
but the tests seem to have something to do with Pango font rendering,
which isn't used to draw UI text any more.
BUG=564879, 457307
Review URL: https://codereview.chromium.org/1678743002
Cr-Commit-Position: refs/heads/master@{#374271}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The StreamMixerAlsa code started using PcmHwParamsTestRate instead of
PcmHwParamsTestRateNear and the mock wasn't updated, so the mock code
started calling snd_pcm_hw_params_test_rate which lead to segfaults. In
addition, after https://codereview.chromium.org/1632393002, the mixer no
longer will use output sample rates below 32kHz, so the unit tests which
specificed a 12.345kHz output will fail. This change corrects both
issues.
BUG=internal b/26429268
Test: build and run alsa_cma_backend_unittests on the CQ staging server
Review URL: https://codereview.chromium.org/1673843004
Cr-Commit-Position: refs/heads/master@{#374256}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(patchset #3 id:40001 of https://codereview.chromium.org/1563053002/ )
Reason for revert:
alsa_cma_backend_unittests is fixed https://codereview.chromium.org/1673843004/
Original issue's description:
> [Chromecast] Disable alsa_cma_backend_unittest on desktop x86.
>
> Internal Cast-CQ crashes when this is run, for unknown reasons. Disable
> this test on the x86 platform so that it is not run while this issue is
> being investigated. This CL should be reverted when this bug is
> resolved.
>
> Bug: b/26429268
>
> BUG=
>
> Committed: https://crrev.com/7f1edfdfb7c282704becfaa5f75db3dbbaa5644b
> Cr-Commit-Position: refs/heads/master@{#367978}
TBR=halliwell@chromium.org,kmackay@chromium.org,servolk@chromium.org,alokp@chromium.org,slan@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=
Review URL: https://codereview.chromium.org/1675043002
Cr-Commit-Position: refs/heads/master@{#374253}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of size_t.
size_t's size depends on the architecture. We need IPCs to match as we're now going to support 32 and 64 bit processes communicating on Android.
This is split off from https://codereview.chromium.org/1619363002/.
BUG=581409
Review URL: https://codereview.chromium.org/1676783002
Cr-Commit-Position: refs/heads/master@{#374205}
|
|
|
|
|
|
|
|
| |
BUG=
Review URL: https://codereview.chromium.org/1678633002
Cr-Commit-Position: refs/heads/master@{#374202}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates audio_video_pipeline_device_unittest.cc to more completely
cover the new CMA backend API. This includes tests for the new state
management, as well as new tests for additional media codecs.
Also, some bugs in the ALSA and default CMA backend implementations
were uncovered and fixed.
BUG= internal b/26496802
Review URL: https://codereview.chromium.org/1649933004
Cr-Commit-Position: refs/heads/master@{#374143}
|
|
|
|
|
|
|
|
|
| |
BUG=571155
TBR=halliwell
Review URL: https://codereview.chromium.org/1676483003
Cr-Commit-Position: refs/heads/master@{#373856}
|
|
|
|
|
|
|
|
| |
BUG=571155
Review URL: https://codereview.chromium.org/1668983004
Cr-Commit-Position: refs/heads/master@{#373840}
|
|
|
|
|
|
|
|
|
|
|
| |
I plan to use it to implement mojo renderer. For more details, see:
https://codereview.chromium.org/1670763003
BUG=571155
Review URL: https://codereview.chromium.org/1667373002
Cr-Commit-Position: refs/heads/master@{#373747}
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is designed to make it easy to enable/disable some or all
of the components that make up the cast receiver code, without needing
to explicitly deal with correct ordering.
BUG=
Review URL: https://codereview.chromium.org/1661063003
Cr-Commit-Position: refs/heads/master@{#373655}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not change |enable_spdy31| and |enable_http2| members of
HttpNetworkSession::Params. Since https://crrev.com/1665703002, these are true
by default. There is no need to set |enable_spdy31| here, and |enable_http2|
really should be enabled (it is a bug that it has not been updated).
Do not change |parse_alternative_services| and
|enable_alternative_service_with_different_host| values either. Setting them
to true is a bug. These features right now are experimental,
HttpNetworSession::Params defaults are false, and they will be changed to true
once these features are launched.
This is a follow-up of https://crrev.com/1651123002.
BUG=329681
Review URL: https://codereview.chromium.org/1664913003
Cr-Commit-Position: refs/heads/master@{#373528}
|
|
|
|
|
|
|
|
| |
BUG=NONE
Review URL: https://codereview.chromium.org/1655403002
Cr-Commit-Position: refs/heads/master@{#373424}
|
|
|
|
|
|
|
|
|
|
| |
The pipeline backend is no-op as of this patch.
BUG=571155
Review URL: https://codereview.chromium.org/1649933002
Cr-Commit-Position: refs/heads/master@{#373374}
|