Enable the hung plugin detector on Win Aura.

Also enable the jumplist code which was similarly disabled.

BUG=330424,330891
R=cpu@chromium.org

Review URL: https://codereview.chromium.org/108413007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242648 0039d316-1c4b-4281-b951-d872f2087c98
Revert 241558 "[Telemetry]: Add V8.MemoryHeapSampleMaximumCommit..."

Seems to have caused page_cycler.intl_ja_zh to time out on the Windows 8 perf bot.

BUG=330909

> [Telemetry]: Add V8.MemoryHeapSampleMaximumCommitted to memory metric.
> 
> BUG=None
> 
> Review URL: https://codereview.chromium.org/99863006

TBR=rmcilroy@chromium.org

Review URL: https://codereview.chromium.org/115173005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242649 0039d316-1c4b-4281-b951-d872f2087c98
Fix color format mapping for RGB24.

The color format media::PIXEL_FORMAT_RGB24 should be mapped to libyuv::FOURCC_24BG in VideoCaptureController.

BUG=330839
R=fbarchard@chromium.org

Review URL: https://codereview.chromium.org/118123003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242650 0039d316-1c4b-4281-b951-d872f2087c98
Support uploading error images to cloud storage directly in Maps test.

This completes the refactoring of the pixel and maps tests, for the time
being. The naming convention of the on-disk error image for the Maps test
is changed to use the FAIL_ prefix to be more clear, since the
archive_gpu_pixel_test_results.py script will not be used anymore when
uploading to cloud storage.

Tested pixel and maps tests, both using on-disk storage and cloud storage,
and both passing and failing scenarios. All are working as expected.

Once this lands, the GPU recipe will be updated right away to switch the
Maps test to use cloud storage, and remove the archive_pixel_test_results
step entirely.

BUG=330774
TBR=bajones@chromium.org

Review URL: https://codereview.chromium.org/112163007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242651 0039d316-1c4b-4281-b951-d872f2087c98
Fix for HttpTransactionDelegate parameter removal from CreateTransaction().

In a previous CL https://codereview.chromium.org/121453002/
CreateTrasaction() method removed one of the parameters HttpTransactionDelegate.
One of the calls were not updated to reflect this change.

NOTRY=true
R=rvargas@chromium.org, tedchoc@chromium.org

Review URL: https://codereview.chromium.org/121963002

Patch from Ramya <cramya@chromium.org>.

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242652 0039d316-1c4b-4281-b951-d872f2087c98
Disable TestReattachAfterCrash on Mac OSX (Once Again)

TestReattachAfterCrash exhibits flaky behavior on Mac OSX. Disable it on Mac OSX.

Crrev #242632 disabled the wrong test.

BUG=163411
R=nasko@chromium.org
TBR=kaznacheev@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/120033003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242653 0039d316-1c4b-4281-b951-d872f2087c98
Replace the GetAssociatedRenderView call with GetAssociatedRenderFrame in InterceptNavigationResourceThrottle.

BUG=304341

Review URL: https://codereview.chromium.org/106203003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242655 0039d316-1c4b-4281-b951-d872f2087c98
Replace the GetAssociatedRenderView call with GetAssociatedRenderFrame in ResourceLoader and SSLClientAuthHandler.

BUG=304341
R=nasko@chromium.org

Review URL: https://codereview.chromium.org/120413003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242656 0039d316-1c4b-4281-b951-d872f2087c98
Implement extension permission dialog experiments.

This CL implements the 12 different screens in the mocks at
http://go/crx-dialog-experiment. Screenshots from the
implementation are at http://go/crx-dialog-experiment-screenshots.

BUG=326733
NOTRY=true

Review URL: https://codereview.chromium.org/103863009

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242657 0039d316-1c4b-4281-b951-d872f2087c98
Use |key_system| in ClearKeyCdm's constructor.

R=jrummell@chromium.org

Review URL: https://codereview.chromium.org/121933002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242658 0039d316-1c4b-4281-b951-d872f2087c98
Do PPB_FileIO Write on the plugin side.

This eliminates IPC for FileIO.Write, instead using the plugin's file descriptor.
Performs the file op on the plugin's thread if blocking, otherwise on the file
thread.

FileIOResources know their maximum written offset after they are opened.
They can thus calculate whether a Write or SetLength operation will extend
this max offset. If so, they call FileSystemResource::RequestQuota. This can
return synchronously or asynchronously, and either returns the requested
amount or 0 in case it can't be satisfied.

FileSystemResource will request a quota reservation from the host, queuing
up unsatisfied requests. The quota reservation will be at least 1MB with this
CL. The main point of a quota reservation is to reduce the number of times
we query the quota system.

Both the FileSystemResource and the host maintain a collection of open files
that are subject to quota. These are kept in sync. Maps that take PP_Resource
to resource or host are used to ensure good performance and make it easier
to keep the resource and host collections synced.

SetLength uses the plugin side machinery to request quota. When its request
is granted, it calls over to the host side as before. This is because of OS X
sandbox restrictions.

For trusted plugins, I assume that this plugin / host checking is sufficient. In
particular, SetLength is performed in the browser process without checking
the length against quota restrictions. We're essentially assuming trusted
plugins don't cheat.

For untrusted plugins, this approach isn't sufficient. NaClMessageScanner
audits the FIleSystem and FileIO message traffic to maintain a parallel
accounting of quota reservation and current file sizes. In addition, we wrap
the native file handle in a NaClDescQuota for files that need quota checking.
This NaClDescQuota uses NaClMessageScanner information to determine
whether or not to allow a Write. We must check at the descriptor level since
the untrusted plugin may bypass our proxy code and use the file handle
directly to Write. We must also fail any attempt to call ftruncate directly.

BUG=194304

Review URL: https://codereview.chromium.org/100703004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242659 0039d316-1c4b-4281-b951-d872f2087c98
Disable test temporarily while I investigate. TBR=nasko

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242660 0039d316-1c4b-4281-b951-d872f2087c98
Fix Android compile

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242661 0039d316-1c4b-4281-b951-d872f2087c98
Replace |reference_id| with |session_id| in ClearKeyCdm.

BUG=224786
R=jrummell@chromium.org

Review URL: https://codereview.chromium.org/121953002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242662 0039d316-1c4b-4281-b951-d872f2087c98
Renable org.chromium.chrome.browser.infobar.InfoBarTest#testInfoBarForPopUp which I reverted in r242660.

TBR=nasko

Review URL: https://codereview.chromium.org/120453005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242663 0039d316-1c4b-4281-b951-d872f2087c98
properly disable test that was disabled before

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242664 0039d316-1c4b-4281-b951-d872f2087c98
Updating trunk VERSION from 1764.0 to 1765.0

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242666 0039d316-1c4b-4281-b951-d872f2087c98
Revert 242659 "Do PPB_FileIO Write on the plugin side."

This seems to have introduced a static initializer on Mac:
http://build.chromium.org/p/chromium/builders/Mac/builds/24153/steps/sizes/logs/stdio

It identifies one in:
  ../../components/nacl/loader/nacl_ipc_adapter.cc
  /Volumes/data/b/build/slave/Mac/build/src/out/Release/libnacl.a(nacl.nacl_ipc_adapter.o)

> Do PPB_FileIO Write on the plugin side.
> 
> This eliminates IPC for FileIO.Write, instead using the plugin's file descriptor.
> Performs the file op on the plugin's thread if blocking, otherwise on the file
> thread.
> 
> FileIOResources know their maximum written offset after they are opened.
> They can thus calculate whether a Write or SetLength operation will extend
> this max offset. If so, they call FileSystemResource::RequestQuota. This can
> return synchronously or asynchronously, and either returns the requested
> amount or 0 in case it can't be satisfied.
> 
> FileSystemResource will request a quota reservation from the host, queuing
> up unsatisfied requests. The quota reservation will be at least 1MB with this
> CL. The main point of a quota reservation is to reduce the number of times
> we query the quota system.
> 
> Both the FileSystemResource and the host maintain a collection of open files
> that are subject to quota. These are kept in sync. Maps that take PP_Resource
> to resource or host are used to ensure good performance and make it easier
> to keep the resource and host collections synced.
> 
> SetLength uses the plugin side machinery to request quota. When its request
> is granted, it calls over to the host side as before. This is because of OS X
> sandbox restrictions.
> 
> For trusted plugins, I assume that this plugin / host checking is sufficient. In
> particular, SetLength is performed in the browser process without checking
> the length against quota restrictions. We're essentially assuming trusted
> plugins don't cheat.
> 
> For untrusted plugins, this approach isn't sufficient. NaClMessageScanner
> audits the FIleSystem and FileIO message traffic to maintain a parallel
> accounting of quota reservation and current file sizes. In addition, we wrap
> the native file handle in a NaClDescQuota for files that need quota checking.
> This NaClDescQuota uses NaClMessageScanner information to determine
> whether or not to allow a Write. We must check at the descriptor level since
> the untrusted plugin may bypass our proxy code and use the file handle
> directly to Write. We must also fail any attempt to call ftruncate directly.
> 
> BUG=194304
> 
> Review URL: https://codereview.chromium.org/100703004

TBR=bbudge@chromium.org

Review URL: https://codereview.chromium.org/122013002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242670 0039d316-1c4b-4281-b951-d872f2087c98
Implement sampling profiler (chromium side change)

Trace-viewer side change is here: https://codereview.appspot.com/39310043

Screenshot of the profiler: http://haraken.info/null/sampling_tracing.png

Design document: https://docs.google.com/a/google.com/document/d/1j39sbA9ECTwFFlxbhSD1EvJnGfYeS5EUJ05yxuku6VY/edit

TBR=phajdan.jr
NOTRY=true

Review URL: https://codereview.chromium.org/109933006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242671 0039d316-1c4b-4281-b951-d872f2087c98
Removing TryPostTask functionality

This is mostly a logical revert of
https://chromiumcodereview.appspot.com/14387002/

Because nobody uses it anymore. At that time there was
resistance about having this but there was a client (the audio code)
that wanted something like this to avoid polling. I don't know what
the audio code does (I so hope is not polling) but certainly is
not using this.

Also see
http://www.youtube.com/watch?v=BQ4yd2W50No

TBR=darin
BUG=none
TEST=none

Review URL: https://codereview.chromium.org/114333006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242672 0039d316-1c4b-4281-b951-d872f2087c98