diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-10 02:43:37 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-10 02:43:37 +0000 |
| commit | d36193eef6a5b874f0924c3f528d49c06ae54888 (patch) | |
| tree | 119d5a1103c9d32e99e2d5234722a2d34c55187d /sandbox | |
| parent | af5a0c6947b3ee5e621bf473ea75dbe2a9258cb3 (diff) | |
| download | chromium_src-d36193eef6a5b874f0924c3f528d49c06ae54888.zip chromium_src-d36193eef6a5b874f0924c3f528d49c06ae54888.tar.gz chromium_src-d36193eef6a5b874f0924c3f528d49c06ae54888.tar.bz2 | |
Revert 109357 - Support tracking of IPC messages as tasks in profiler
This was previously landed as 108752, but reverted in 109004
by Joi to try to stop flaky failures in ASAN bot when
running browser_tests..
The failures included:
IncognitoSplitMode
TwoExtensionsCrashBothAtOnce
TwoExtensionsOneByOne
AutoUpdate
CognitoNoFile
IncognitoNoFile
OnChangedNotificationsBetweenBackgroundPages
SplitModeIncognito
I'm now landing 1 hook at a time back into the build, to
see which one(s) tickle flakiness.
The other hooks are commented out, so that I can
try several alternatives and figure out what is
tickling the problem.
The restructuring of the code was already landed, and did
not *appear* to induce the failures. Hence it is likely
that one of the IPC hooks is the problem.
If I need to, I'll TBR various owners, since I've already gotten permission for this landing.
r=rtenneti
Review URL: http://codereview.chromium.org/8499039
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/8506037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109371 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sandbox')
0 files changed, 0 insertions, 0 deletions