|
|
Created:
4 years, 5 months ago by Will Harris Modified:
4 years, 5 months ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMake base::TerminateBecauseOutOfMemory call RaiseException on Windows.
This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc
BUG=614440
Committed: https://crrev.com/3850a4d9df7a7e6f1c2d48715362de6bac01523a
Cr-Commit-Position: refs/heads/master@{#407315}
Patch Set 1 #Patch Set 2 : fix unittests #
Total comments: 1
Patch Set 3 : rejig #Patch Set 4 : non-windows type #Patch Set 5 : make win only #Patch Set 6 : implement in memory_stubs #
Dependent Patchsets: Messages
Total messages: 40 (23 generated)
The CQ bit was checked by wfh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
Description was changed from ========== Make base::TerminateBecauseOutOfMemory raise exception on Windows. BUG=614440 ========== to ========== Make base::TerminateBecauseOutOfMemory raise exception on Windows. BUG=614440 ==========
wfh@chromium.org changed reviewers: + mark@chromium.org
wfh@chromium.org changed reviewers: + mtklein@chromium.org
Description was changed from ========== Make base::TerminateBecauseOutOfMemory raise exception on Windows. BUG=614440 ========== to ========== Make base::TerminateBecauseOutOfMemory call RaiseException on Windows. This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc BUG=614440 ==========
PTAL - missed an OOM handler.
the Skia bit (very) lgtm
LGTM https://codereview.chromium.org/2173463002/diff/20001/base/process/memory_win.cc File base/process/memory_win.cc (right): https://codereview.chromium.org/2173463002/diff/20001/base/process/memory_win... base/process/memory_win.cc:41: const DWORD kOomExceptionCode = 0xe0000008; Now you’ve got to update the comment in Breakpad to point to this file. :)
actually I need this code to be exposed out of this file, as it's needed by base/process/kill_win.cc to decode the right termination status, so I'm going to move it back out into a header. I'll re-upload a CL soon! Kill two birds with one stone!
mark - this is enough different it probably needs another quick review. I made the OOM exception code not wrapped in OS_WIN because it would mean anything that wanted to use it would have to be wrapped in OS_WIN too and it gets ugly really quick... otherwise the only functional change is that OnNoMemory is NOINLINE just to make sure it appears in its own stack, which it does already but just extra safety - crash/12b34f8900000000
This is LGTM, except Will Harris wrote: > mark - this is enough different it probably needs another quick review. I made > the OOM exception code not wrapped in OS_WIN because it would mean anything that > wanted to use it would have to be wrapped in OS_WIN too and it gets ugly really > quick... I don’t agree with this. I think it should be in an OS_WIN #ifdef, and it looks like everything that uses it here is also already Windows-only, so that shouldn’t be a problem.
On 2016/07/22 01:51:02, Mark Mentovai wrote: > This is LGTM, except > > Will Harris wrote: > > mark - this is enough different it probably needs another quick review. I made > > the OOM exception code not wrapped in OS_WIN because it would mean anything > that > > wanted to use it would have to be wrapped in OS_WIN too and it gets ugly > really > > quick... > > I don’t agree with this. I think it should be in an OS_WIN #ifdef, and it looks > like everything that uses it here is also already Windows-only, so that > shouldn’t be a problem. understood - and you're owner, but future code https://codereview.chromium.org/2172013002/ uses this and will end up being massively OS_WIN-deffed including other stuff in base and grit resources. So let me know either way and I can do what you want.
On 2016/07/22 02:01:08, Will Harris wrote: > On 2016/07/22 01:51:02, Mark Mentovai wrote: > > This is LGTM, except > > > > Will Harris wrote: > > > mark - this is enough different it probably needs another quick review. I > made > > > the OOM exception code not wrapped in OS_WIN because it would mean anything > > that > > > wanted to use it would have to be wrapped in OS_WIN too and it gets ugly > > really > > > quick... > > > > I don’t agree with this. I think it should be in an OS_WIN #ifdef, and it > looks > > like everything that uses it here is also already Windows-only, so that > > shouldn’t be a problem. > > understood - and you're owner, but future code > https://codereview.chromium.org/2172013002/ uses this and will end up being > massively OS_WIN-deffed including other stuff in base and grit resources. So let > me know either way and I can do what you want. actually in support of your argument, I originally thought other variables e.g. kMaxOomScore were not wrapped in #if defined but they actually are, so it does make sense to wrap this one too... I can grudgingly do this and change the other CL. :)
Patchset #5 (id:80001) has been deleted
LGTM here now
The CQ bit was checked by wfh@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from mtklein@chromium.org Link to the patchset: https://codereview.chromium.org/2173463002/#ps100001 (title: "make win only")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
The CQ bit was checked by wfh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
Patchset #6 (id:120001) has been deleted
The CQ bit was checked by wfh@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from mark@chromium.org, mtklein@chromium.org Link to the patchset: https://codereview.chromium.org/2173463002/#ps140001 (title: "implement in memory_stubs")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
On 2016/07/22 22:19:06, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) not my CL! :)
The CQ bit was checked by wfh@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Make base::TerminateBecauseOutOfMemory call RaiseException on Windows. This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc BUG=614440 ========== to ========== Make base::TerminateBecauseOutOfMemory call RaiseException on Windows. This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc BUG=614440 ==========
Message was sent while issue was closed.
Committed patchset #6 (id:140001)
Message was sent while issue was closed.
Description was changed from ========== Make base::TerminateBecauseOutOfMemory call RaiseException on Windows. This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc BUG=614440 ========== to ========== Make base::TerminateBecauseOutOfMemory call RaiseException on Windows. This is a follow-on CL to https://codereview.chromium.org/2130293003 which added the RaiseException call in memory_win.cc but missed memory.cc BUG=614440 Committed: https://crrev.com/3850a4d9df7a7e6f1c2d48715362de6bac01523a Cr-Commit-Position: refs/heads/master@{#407315} ==========
Message was sent while issue was closed.
Patchset 6 (id:??) landed as https://crrev.com/3850a4d9df7a7e6f1c2d48715362de6bac01523a Cr-Commit-Position: refs/heads/master@{#407315} |