← Back to team overview

kernel-packages team mailing list archive

[Bug 1022172] Re: Not enough memory to kill process


Fred, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal (Applications->Accessories->Terminal), as it will
automatically gather and attach updated debug information to this

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:

where VERSION-NUMBER is the version number of the kernel you tested. For example:

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:

If the mainline kernel does not fix this bug, please add the following tags:

As well, please remove the tag:

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your

** Tags added: needs-kernel-logs needs-upstream-testing regression-

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Not enough memory to kill process

Status in “linux” package in Ubuntu:

Bug description:
  So I was running a process that had a memory leak (1.9 gb RAM) of which I was unaware of, then I was starting up a virtual machine in VirtualBox.
  My system runs out of memory and things go awry, VirtualBox gets into guru meditation and crashes and the whole system gets unusable.

  I try to kill VirtualBox to no avail.

  $ killall virtualbox
  bash: fork: Cannot allocate memory

  I have no memory. So I try to free memory. But I can't free memory.
  Because I have no memory.

  So instead of greedily consuming every single little last byte of
  memory, please reserve a couple of puny bytes so that I can run 'kill'
  or 'killall' when things go awry.

To manage notifications about this bug go to: