That is of course your prerogative, but as a developer I would have hoped you would consider helping the VB developers identify and resolve the problem rather than just posting implying that they have just not done anything about it and do not do proper testing I have found the VirtualBox development team to be generally responsive when presented with evidence of a problem and the associated diagnostics.I will open up a ticket and as a developer myself I am fully aware of the processes. However, when you need things to just work, its just sometimes better to get your cash out and stop wasting your time.
I have been running Mavericks since 10.9.0 and am currently on 10.9.4 and I have used all VirtualBox 4.3 versions through to the current 4.3.14 on Mavericks. I experience the problem severely in early 4.3.x VB versions but the issue was resolved around 4.3.6 or so I believe (I cannot recall exactly). One point to note - if you just install the new version of VirtualBox over the old one (what most of us tend to do) then it is possible that the kernel extensions do not get upgraded properly. I have seen this happen myself. I would recommend that you try the following, if you have not already done so:
1. Uninstall VirtualBox completely using the uninstall script that is part of the installer disk image.
2. Reboot your machine.
3. Re-install VirtualBox 4.2.14 and the extension pack (if you use it).
You may well find that this fixes your problem. If not then opening a ticket is the best way to get this fixed for yourself and anyone else who is still experiencing this very annoying problem.