|
|
Created:
4 years, 7 months ago by erikchen Modified:
4 years, 7 months ago CC:
chromium-reviews, darin-cc_chromium.org, jam, rickyz+watch_chromium.org, Avi (use Gerrit), chrome-blacklisting-announce_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionBlacklist rooksbas.dll in sandboxed processes
This is a source of many renderer hangs. See bug for more details.
BUG=609262
Committed: https://crrev.com/9a3648a17691625a13ee8acdb798813280193fb3
Cr-Commit-Position: refs/heads/master@{#395377}
Patch Set 1 #
Messages
Total messages: 26 (11 generated)
erikchen@chromium.org changed reviewers: + scottmg@chromium.org
scottmg: Please review.
The CQ bit was checked by erikchen@chromium.org to run a CQ dry run
erikchen@chromium.org changed reviewers: + avi@chromium.org
+avi, for an actual content/ OWNER
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2004573003/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2004573003/1
Description was changed from ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 ========== to ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 ==========
scottmg@chromium.org changed reviewers: + jschuh@chromium.org, wfh@chromium.org - avi@chromium.org
sandbox_win is noparent, wfh or jschuh can hook you up. lgtm [ i would 'not l-g-t-m' the rollback of this >:-( ]
On 2016/05/20 23:03:49, scottmg (ooo until 24may) wrote: > sandbox_win is noparent, wfh or jschuh can hook you up. > > lgtm > > [ > i would 'not l-g-t-m' the rollback of this >:-( > ] lgtm but please notify csharp@ as he knows full process for this.
erikchen@chromium.org changed reviewers: + csharp@chromium.org, taviso@google.com
+csharp, taviso. This is a stability issue, and this particular module was recently blacklisted/unblacklisted: https://codereview.chromium.org/2004573003/ Should I do anything beyond sending email to chrome-blacklisting-announce@chromium.org? (https://www.chromium.org/Home/third-party-developers#TOC-Google-Chrome-s-DLL-...)
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
avi@chromium.org changed reviewers: + avi@chromium.org
lgtm
On 2016/05/22 00:03:04, Avi wrote: > lgtm We're cutting M51 tomorrow, so this has to land soon. I haven't been able to get a hold of taviso@ or csharp@. I'm going to land this CL, merge to M51, and send mail to the appropriate lists.
The CQ bit was checked by erikchen@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2004573003/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2004573003/1
LGTM, what they're doing makes no sense whatsoever.
This message is to notify to chrome-blacklisting-announce@chromium.org that these two DLLs are being blacklisted from Chromium renderer processes: rooksbas.dll rooksbas_x64.dll
Message was sent while issue was closed.
Description was changed from ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 ========== to ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 ========== to ========== Blacklist rooksbas.dll in sandboxed processes This is a source of many renderer hangs. See bug for more details. BUG=609262 Committed: https://crrev.com/9a3648a17691625a13ee8acdb798813280193fb3 Cr-Commit-Position: refs/heads/master@{#395377} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/9a3648a17691625a13ee8acdb798813280193fb3 Cr-Commit-Position: refs/heads/master@{#395377}
Message was sent while issue was closed.
A revert of this CL (patchset #1 id:1) has been created in https://codereview.chromium.org/2003373003/ by erikchen@chromium.org. The reason for reverting is: This causes full browser hangs when the Trusteer Rapport product is enabled. We probably need to also blacklist dlls from the browser process.. |