[Bug 219556] emulators/virtualbox-ose: VBoxSVC consumes 100% CPU and does not exit
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu May 25 20:54:27 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219556
Bug ID: 219556
Summary: emulators/virtualbox-ose: VBoxSVC consumes 100% CPU
and does not exit
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: vbox at FreeBSD.org
Reporter: la5lbtyi at aon.at
Assignee: vbox at FreeBSD.org
Flags: maintainer-feedback?(vbox at FreeBSD.org)
Since a few days (I believe since the upgrade of mesa to 17.1.0) VBoxSVC
continuously consumes 100% CPU and does not shut down after all sessions have
closed.
This happens if any graphical window is used (VirtualBox). If using only
VBoxHeadless, VBoxSvc behaves normally.
Also, this happens on one of two systems only: The affected one has an Intel
CPU and uses an Nvidia graphics card + proprietary driver, whereas the normal
one uses an AMD CPU and displays graphical output over the network (X11
connection).
# top -Utest
last pid: 9924; load averages: 0.88, 0.90, 1.40 up 0+05:30:35 22:43:46
122 processes: 2 running, 119 sleeping, 1 zombie
CPU: 0.5% user, 12.5% nice, 0.4% system, 0.0% interrupt, 86.5% idle
Mem: 820M Active, 2747M Inact, 5324M Wired, 109M Buf, 15G Free
ARC: 2998M Total, 618M MFU, 2329M MRU, 444K Anon, 11M Header, 38M Other
Swap: 9216M Total, 9216M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
9916 test 14 25 5 172M 50820K select 5 0:15 103.65% VBoxSVC
9911 test 9 26 5 394M 107M select 2 0:01 0.08% VirtualBo
9917 test 1 20 0 30364K 7076K CPU5 5 0:00 0.05% top
9914 test 1 25 5 123M 43400K select 0 0:00 0.02% VBoxXPCOM
9898 test 1 20 0 75696K 13228K select 0 0:00 0.01% xterm
9899 test 1 20 0 35068K 8796K pause 4 0:00 0.00% zsh
When exiting VirtualBox via the "exit" menu command, the window vanishes, but
VBoxSVC continues to run at 100% CPU, and the VirtualBox process remains (at
0%). In this case, VBoxSVC can be killed -1, which will then also terminate
VirtualBox and VBoxXPCOM.
All ports up-to-date as of now.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list