It took quite a while to locate this bug on Launchpad due to the non-descriptiveness of the issue: the only thing you get to see is "killed". As there are 14 people already listed here as affected, it is to be expected that the total number of users affected is large.
I am getting this bug while trying to pull percona-server under FC17 running in vbox with 2Gb of memory assigned.
When trying to up the memory assigned to the vm, the pull quickly consumed 4+Gb and eventually lead to host os/vbox OOM errors!
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1576 - 20 0 4576m 4.2g 3872 S 14.6 74.6 2:29.86 bzr
Re-questing re-triage. This bug is major.
It took quite a while to locate this bug on Launchpad due to the non-descriptiveness of the issue: the only thing you get to see is "killed". As there are 14 people already listed here as affected, it is to be expected that the total number of users affected is large.
I am getting this bug while trying to pull percona-server under FC17 running in vbox with 2Gb of memory assigned.
When trying to up the memory assigned to the vm, the pull quickly consumed 4+Gb and eventually lead to host os/vbox OOM errors!
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1576 - 20 0 4576m 4.2g 3872 S 14.6 74.6 2:29.86 bzr
Could we have this looked at?
bzr version: 2.5.0
uname: 3.4.6-2.fc17.x86_64
vbox: 4.1.18 r78361 (host OS: Win7 HP SP1)