Guests aborting possibly due to core audio device change on host

[Mike467]

Had been using 5.0.2 and it was working flawlessly. Upgraded to 5.0.10. Guests now often abort after a few hours use, overnight, or even sooner. No direct correlation to sleep/resume cycles.

Note: I have a usb audio device attached. (attached log shows possible cause of aborts (my guess): repeatedly changing usb audio device). But this problem didn't occur with 5.02 with exactly the same hardware attached (it's a topping vx1).

Guest additions are present (and updated to 5.010). No extensions pack present (e.g. usb for the guest). Now considering: (a) ditching the usb audio device. (b) downgrading to 5.02. Any pointers appreciated thanks.

[Mike467]

Same guest, after downgrade to 5.0.2

[Mike467]

UPDATE: Have backed up my vm's and installed 5.0.2 (on top of 5.0.10, without uninstalling it, this being quick; realising might not be wise). Version number now reads 5.0.2 on cmd line and gui. Booting the same guest, this time repeated core audio device changed messages are absent in the log (second attachment above). Will update this thread in 24hrs in case problem solved.

[aeichner]

We fixed an issue related to changing input or output devices which could cause random memory corruption. Please try with the latest test build from here. Thanks!

[Frank Mehnert]

Please reopen if still relevant with VBox 5.0.12.