Application Hangs After Several Hours

[JoelProminic]

Extracted from #168

Testing in 1.5.15, I'm seeing that the application hangs after running for some time. The CPU usage is low, but the application is unusable. I'm not sure if this problem is directly related to the above fix. We can address this in a separate issue if we want to push forward with the 1.6.0 release.

@MarkProminic @piotrzarzycki21

Originally posted by @JoelProminic in #168

I'm continuing to see this error in 1.6.0, so I'm creating a separate issue. I had sent Mark and example log for review (note that the logs also seem unusually large).

This still does not seem to correspond to an increased CPU load.

It takes 4-6 hours for the problem to trigger. If I start Super.Human.Installer at the beginning of the work day, it is hanging by the end of the day. I'm not sure yet if this issue requires running an action (like starting a VM) - I'll let you know if I confirm this one way or another.

I can just restart Super.Human.Installer to resolve the problem.

[MarkProminic]

Can you time the following commands :

# Command 1: Vagrant global status
time /usr/local/bin/vagrant global-status --machine-readable

# Command 2: VirtualBox list VMs (this is the big one)
time /usr/local/bin/VBoxManage list vms --long

# Command 3: Vagrant version
time /usr/local/bin/vagrant -v

# Command 4: VirtualBox version  
time /usr/local/bin/VBoxManage -V

# Command 5: Git version
time /usr/bin/git --version

# Command 6: Rsync version (Mac/Linux only)
time rsync --version

[JoelProminic]

These commands all seem reasonably fast:

/usr/local/bin/vagrant global-status --machine-readable  0.66s user 0.22s system 100% cpu 0.872 total

/usr/local/bin/VBoxManage list vms --long  0.11s user 0.16s system 59% cpu 0.459 total

/usr/local/bin/vagrant -v  0.07s user 0.02s system 93% cpu 0.099 total

/usr/local/bin/VBoxManage -V  0.01s user 0.01s system 84% cpu 0.016 total

/usr/bin/git --version  0.01s user 0.01s system 82% cpu 0.017 total

rsync --version  0.00s user 0.00s system 87% cpu 0.003 total

I started SHI 1.6.0 last night without running anything, and it was still responding properly this morning. So, it seems like this requires at least one action to trigger, similar to #168