|
|
Created:
5 years, 9 months ago by hichris123 Modified:
5 years, 9 months ago CC:
chromium-reviews, creis+watch_chromium.org, grt+watch_chromium.org, nasko+codewatch_chromium.org, jam, darin-cc_chromium.org, wfh+watch_chromium.org, erikwright+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionOnly enable the Low Box token on Windows 8 and 8.1
r319208 added the Low Box token to PreSpawnTarget. For some reason, this doesn't play well with Windows 10 preview builds, so this CL selectively enables the feature on Windows 8 & 8.1
BUG=464779, 455496
Committed: https://crrev.com/b5c098bbecc0cf42863cec0aa24651b00642b3af
Cr-Commit-Position: refs/heads/master@{#319790}
Patch Set 1 #Patch Set 2 : Fix typo in comment #Patch Set 3 : Don't change windows_version, only match 8 & 8.1 #
Total comments: 1
Patch Set 4 : ==, not != #Messages
Total messages: 19 (3 generated)
hichris123@gmail.com changed reviewers: + cpu@chromium.org, shrikant@chromium.org
cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to load, see bug 464779.
On 2015/03/08 15:52:19, hichris123 wrote: > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to load, see > bug 464779. Thanks for the CL. Please remove windows_version.cc file, modified for Windows 10 builds earlier than 9926.
On 2015/03/09 00:07:03, Shrikant Kelkar wrote: > On 2015/03/08 15:52:19, hichris123 wrote: > > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to load, > see > > bug 464779. > > Thanks for the CL. Please remove windows_version.cc file, modified for Windows > 10 builds earlier than 9926. Okay, but that means Chrome will not work on older Technical Preview builds still.
On 2015/03/09 00:12:21, hichris123 wrote: > On 2015/03/09 00:07:03, Shrikant Kelkar wrote: > > On 2015/03/08 15:52:19, hichris123 wrote: > > > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to load, > > see > > > bug 464779. > > > > Thanks for the CL. Please remove windows_version.cc file, modified for Windows > > 10 builds earlier than 9926. > > Okay, but that means Chrome will not work on older Technical Preview builds > still. How about changing the test in content/browser/renderer_host/render_process_host_impl.cc to match only win8, especially given we only have not coverage on win8 at the moment. We can add win10 support once we have better coverage and it gets closer to rtm.
On 2015/03/09 00:16:21, Will Harris wrote: > On 2015/03/09 00:12:21, hichris123 wrote: > > On 2015/03/09 00:07:03, Shrikant Kelkar wrote: > > > On 2015/03/08 15:52:19, hichris123 wrote: > > > > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to > load, > > > see > > > > bug 464779. > > > > > > Thanks for the CL. Please remove windows_version.cc file, modified for > Windows > > > 10 builds earlier than 9926. > > > > Okay, but that means Chrome will not work on older Technical Preview builds > > still. > > How about changing the test in > content/browser/renderer_host/render_process_host_impl.cc to match only win8, > especially given we only have not coverage on win8 at the moment. > > We can add win10 support once we have better coverage and it gets closer to rtm. *Just* Win8 or 8.1 too? The reason why I ask is older Win10 builds are identified by Chrome as Win8.1, so we could either a) change windows_version, b) match only Win8 and not 8.1, or c) match Win 8 and 8.1, and ignore users on older versions of the preview.
On 2015/03/09 00:18:41, hichris123 wrote: > On 2015/03/09 00:16:21, Will Harris wrote: > > On 2015/03/09 00:12:21, hichris123 wrote: > > > On 2015/03/09 00:07:03, Shrikant Kelkar wrote: > > > > On 2015/03/08 15:52:19, hichris123 wrote: > > > > > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to > > load, > > > > see > > > > > bug 464779. > > > > > > > > Thanks for the CL. Please remove windows_version.cc file, modified for > > Windows > > > > 10 builds earlier than 9926. > > > > > > Okay, but that means Chrome will not work on older Technical Preview builds > > > still. > > > > How about changing the test in > > content/browser/renderer_host/render_process_host_impl.cc to match only win8, > > especially given we only have not coverage on win8 at the moment. > > > > We can add win10 support once we have better coverage and it gets closer to > rtm. > > *Just* Win8 or 8.1 too? > > The reason why I ask is older Win10 builds are identified by Chrome as Win8.1, > so we could either a) change windows_version, b) match only Win8 and not 8.1, or > c) match Win 8 and 8.1, and ignore users on older versions of the preview. Win 8 and Win 8.1
On 2015/03/09 00:34:20, Will Harris wrote: > On 2015/03/09 00:18:41, hichris123 wrote: > > On 2015/03/09 00:16:21, Will Harris wrote: > > > On 2015/03/09 00:12:21, hichris123 wrote: > > > > On 2015/03/09 00:07:03, Shrikant Kelkar wrote: > > > > > On 2015/03/08 15:52:19, hichris123 wrote: > > > > > > cpu, Shrikant: PTAL. This has been causing Canary on Windows 10 not to > > > load, > > > > > see > > > > > > bug 464779. > > > > > > > > > > Thanks for the CL. Please remove windows_version.cc file, modified for > > > Windows > > > > > 10 builds earlier than 9926. > > > > > > > > Okay, but that means Chrome will not work on older Technical Preview > builds > > > > still. > > > > > > How about changing the test in > > > content/browser/renderer_host/render_process_host_impl.cc to match only > win8, > > > especially given we only have not coverage on win8 at the moment. > > > > > > We can add win10 support once we have better coverage and it gets closer to > > rtm. > > > > *Just* Win8 or 8.1 too? > > > > The reason why I ask is older Win10 builds are identified by Chrome as Win8.1, > > so we could either a) change windows_version, b) match only Win8 and not 8.1, > or > > c) match Win 8 and 8.1, and ignore users on older versions of the preview. > > Win 8 and Win 8.1 Okay, uploaded a new changeset.
wfh@chromium.org changed reviewers: + wfh@chromium.org
please also update the CL description & title to reflect more accurately what this CL does - something like 'Only enable Low Box token on Windows 8 and 8.1' https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... File content/browser/renderer_host/render_process_host_impl.cc (right): https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... content/browser/renderer_host/render_process_host_impl.cc:334: base::win::GetVersion() != base::win::VERSION_WIN8_1) { I think you mean == here?
On 2015/03/09 01:18:25, Will Harris wrote: > please also update the CL description & title to reflect more accurately what > this CL does - something like 'Only enable Low Box token on Windows 8 and 8.1' > > https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... > File content/browser/renderer_host/render_process_host_impl.cc (right): > > https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... > content/browser/renderer_host/render_process_host_impl.cc:334: > base::win::GetVersion() != base::win::VERSION_WIN8_1) { > I think you mean == here? Er, yeah, that teaches me to double-check what I'm doing. ;) Fixed.
On 2015/03/09 01:21:17, hichris123 wrote: > On 2015/03/09 01:18:25, Will Harris wrote: > > please also update the CL description & title to reflect more accurately what > > this CL does - something like 'Only enable Low Box token on Windows 8 and 8.1' > > > > > https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... > > File content/browser/renderer_host/render_process_host_impl.cc (right): > > > > > https://codereview.chromium.org/986933002/diff/40001/content/browser/renderer... > > content/browser/renderer_host/render_process_host_impl.cc:334: > > base::win::GetVersion() != base::win::VERSION_WIN8_1) { > > I think you mean == here? > > Er, yeah, that teaches me to double-check what I'm doing. ;) Fixed. Also updated the CL description. I think I need to read *everything* closer now. :P
lgtm
On 2015/03/09 20:47:12, cpu wrote: > lgtm I'll send this to the CQ, then, unless anyone has any objections.
The CQ bit was checked by wfh@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/986933002/60001
I CQed it - I think you need to be a committer to tick the box.
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/b5c098bbecc0cf42863cec0aa24651b00642b3af Cr-Commit-Position: refs/heads/master@{#319790} |