Hyperkit leaks about hyperkit HOT 5 CLOSED

@ijc25 I've had issues when memory appears to be full docker quits responding to various commands (like ps or being able to download images). The only way to fix it is the restart the process so memory goes back down.

from hyperkit.

Sounds from your terse description like you are referring to something like the issues described in docker/for-mac#178 and docker/for-mac#781? That is the OSX process is actually using that memory (as guest RAM) and has not "leaked" in the normal sense.

The first comment on the former is basically an accurate summary of where we are right now with this. Only if you are seeing either actual memory leaks (that is, memory which the hypervisor has actually lost track of) or memory allocated to the hyperkit process which is unswappable (which would manifest as the RSS remaining high even when the VM is idle and there are other memory pressures in the system) would we currently consider this an issue. If you are aware of either scenario occurring then we would be grateful of the details.

For those who are concerned about swappable memory allocated to virtual machines (i.e. the VSZ of the process) the usual answer is ballooning, which in this context would start with an implementation of the virtio-balloon backend in hyperkit. However ballooning functionality in the hypervisor is only a building block and other higher level code would also be needed to manage this functionality in a way which did not compromise functionality/stability/reliability of projects which use hyperkit (or to put it more concretely and avoid giving false hope/commitment: adding ballooning functionality in hyperkit would not automatically mean it would be activated by Docker for mac, it would need careful evaluation and integration work by the docker for mac team first).

We currently don't have any plans to work on anything related to this but if, given the caveats expressed here, you are still interested then PRs to implement virtio-ballooning in hyperkit would be welcome.

from hyperkit.

@jhorwit2 Please open a new ticket against docker/for-mac about the issue you are seeing including a diagnostic bundle upload etc. Easiest way to do that is to use the "Diagnostics & Feedback" item in the Whale menu.

Closing this issue since there has been no further response from the OP.

from hyperkit.

Ive noticed this happening to me sometimes when i've accidentally tried to interact with a really large image. Restarting docker, and clearing out images doesn't seem to help. Doing a factory restart on docker does. I think it tries to access some of the same volume information between restarts.

from hyperkit.

@kyprifog please file an issue on docker/for-mac unless you are certain that this is an issue with hyperkit itself. If you think it is hyperkit itself, please provide more details.

from hyperkit.