virtualbox.org

---

ModEdit; related ticket: #18049: High cpu usage logd after sleep while using microphone, audio does not work

---

1. Start up a virtual box Windows 7 VM on a Mac OS high Sierra host
2. Start-up activity monitor on Mac OS
3. Start up a sound recorder recording
4. Put the Mac OS to sleep
5. Wajit five seconds and then wake up the Mac
6. Speak anything into the microphone for a second
7. Watch the CPU usage rise as shown in the screenshot below. Also, sound recorder inside the Windows VM will not be picking up any audio.

Note that you can replace putting the host machine to sleep was creating a virtual machine snapshot, and the exact same problem will occur.

This bug is very annoying for me because I use Dragon NaturallySpeaking inside a virtual machine, because I am unable to use my arms for a large portion of typing. This bug happens every time I put my computer to sleep while Dragon is open (i.e. always), so after I wake up my computer I have two close and reopen Dragon which takes an additional minute. Also, when I don't have my activity monitor running, I won't notice the high CPU usage, and my battery will drop like hell! Very annoying !

This was replicated on a MacBook Pro 13 2015, and a MacBook Pro 15 and 2018 on the latest version of Mac OS high Sierra, with a Windows 7 virtual machine, and virtual box version 5.1.22, and 5.2.22.

Can anyone else replicate this issue? I reported this bug here https://www.virtualbox.org/ticket/18049 over a month ago and heard from no one

dylanthepiguy2 wrote:Can anyone else replicate this issue?

Yes. It has been reported several times. In theory it has been fixed with 5.2.22, but I've seen a couple of reports already that complain that it's not. Please confirm/refute this claim. Thanks...

There is a new 5.2 test build 126798 on the Testbuild page which one of the developers has suggested may fix some of the similar issues. Please download the build here: https://www.virtualbox.org/wiki/Testbuilds

-Andy.

The build you mentioned does not appear to fix the problem

I think a developer got their wings back...
Thank you for reporting back!