Opened 4 years ago
Last modified 4 years ago
#19562 assigned defect
VBoxClient on Linux : leaves defunct xrandr zombies
| Reported by: | dry | Owned by: | gombara |
|---|---|---|---|
| Component: | guest additions/x11/graphics | Version: | VirtualBox 6.1.6 |
| Keywords: | cvt xrandr defunct vmsvga | Cc: | |
| Guest type: | Linux | Host type: | all |
Description
In this new version the VBox guest additions for Linux have un-desirable working effect in that it leaves many defunct or zombies, somewhere along the chain of xrandr invocation.
Below is snippets from pstree and ps.
├─2*[VBoxClient───VBoxClient───2*[{VBoxClient}]]
├─VBoxClient───VBoxClient───3*[{VBoxClient}]
├─VBoxClient───VBoxClient─┬─29*[cvt]
│ ├─30*[sh]
│ ├─17*[xrandr]
│ └─2*[{VBoxClient}]
1535 ? 00:00:00 VBoxClient 1536 ? 00:00:05 VBoxClient 1544 ? 00:00:00 VBoxClient 1545 ? 00:00:00 VBoxClient 1550 ? 00:00:00 VBoxClient 1551 ? 00:00:22 VBoxClient 1557 ? 00:00:00 VBoxClient 1558 ? 00:00:00 VBoxClient 1559 ? 00:00:00 xrandr <defunct> 1562 ? 00:00:00 sh <defunct> 1564 ? 00:00:00 cvt <defunct> 1601 ? 00:00:00 xrandr <defunct> 1631 ? 00:00:00 sh <defunct> 1634 ? 00:00:00 cvt <defunct> 1638 ? 00:00:00 lxclipboard 1665 ? 00:00:00 xrandr <defunct> 2651 ? 00:00:00 sh <defunct> 2653 ? 00:00:00 cvt <defunct> 2663 ? 00:00:00 sh <defunct> 2666 ? 00:00:00 xrandr <defunct> 2683 ? 00:00:00 sh <defunct> 2685 ? 00:00:00 cvt <defunct> 2695 ? 00:00:00 sh <defunct> 2697 ? 00:00:00 cvt <defunct> 2708 ? 00:00:00 xrandr <defunct> 2725 ? 00:00:00 sh <defunct> 2727 ? 00:00:00 cvt <defunct> 2737 ? 00:00:00 sh <defunct> 2739 ? 00:00:00 cvt <defunct> 2750 ? 00:00:00 xrandr <defunct> 2783 ? 00:00:00 sh <defunct> 2785 ? 00:00:00 cvt <defunct> 2795 ? 00:00:00 sh <defunct> 2797 ? 00:00:00 cvt <defunct> 2808 ? 00:00:00 xrandr <defunct> 5735 ? 00:00:00 sh <defunct> 5737 ? 00:00:00 cvt <defunct> 5747 ? 00:00:00 sh <defunct> 5749 ? 00:00:00 cvt <defunct> 5760 ? 00:00:00 xrandr <defunct> 5793 ? 00:00:00 sh <defunct> 5795 ? 00:00:00 cvt <defunct> 5805 ? 00:00:00 sh <defunct> 5807 ? 00:00:00 cvt <defunct> 5818 ? 00:00:00 xrandr <defunct> 5842 ? 00:00:00 dhclient 5853 ? 00:00:00 sh <defunct> 5855 ? 00:00:00 cvt <defunct> 5865 ? 00:00:00 sh <defunct> 5867 ? 00:00:00 cvt <defunct> 5879 ? 00:00:00 xrandr <defunct> 5912 ? 00:00:00 sh <defunct> 5914 ? 00:00:00 cvt <defunct> 5924 ? 00:00:00 sh <defunct> 5926 ? 00:00:00 cvt <defunct> 5937 ? 00:00:00 xrandr <defunct> 5964 ? 00:00:00 sh <defunct> 5966 ? 00:00:00 cvt <defunct> 5976 ? 00:00:00 sh <defunct> 5978 ? 00:00:00 cvt <defunct> 5989 ? 00:00:00 xrandr <defunct> 6022 ? 00:00:00 sh <defunct> 6024 ? 00:00:00 cvt <defunct> 6034 ? 00:00:00 sh <defunct> 6036 ? 00:00:00 cvt <defunct> 6047 ? 00:00:00 xrandr <defunct> 6074 ? 00:00:00 sh <defunct> 6076 ? 00:00:00 cvt <defunct> 6086 ? 00:00:00 sh <defunct> 6088 ? 00:00:00 cvt <defunct> 6099 ? 00:00:00 xrandr <defunct> 6132 ? 00:00:00 sh <defunct> 6134 ? 00:00:00 cvt <defunct> 6144 ? 00:00:00 sh <defunct> 6146 ? 00:00:00 cvt <defunct> 6157 ? 00:00:00 xrandr <defunct> 6176 ? 00:00:00 sh <defunct> 6178 ? 00:00:00 cvt <defunct> 6188 ? 00:00:00 sh <defunct> 6190 ? 00:00:00 cvt <defunct> 6201 ? 00:00:00 xrandr <defunct> 6234 ? 00:00:00 sh <defunct> 6236 ? 00:00:00 cvt <defunct> 6246 ? 00:00:00 sh <defunct> 6248 ? 00:00:00 cvt <defunct> 6259 ? 00:00:00 xrandr <defunct>
Seems it's 'trying to do something..', when I do something - I haven't spent time checking exactly what, but could be the enabling and/or moving the virtual monitor. However, from memory at least one defunct group appears straight after boot and with first & only one virtual monitor is on. It grows in number of traces from there.
This was not the case for older VBox, quite likely from v 6.1.4 and higher.
My guest is Linux Fedora 30 64bit.
Change History (11)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Update.
So right after the boot & first screen starts, it leaves this much :
ps -A | grep defu 1590 ? 00:00:00 xrandr <defunct> 1594 ? 00:00:00 sh <defunct> 1598 ? 00:00:00 cvt <defunct> 1628 ? 00:00:00 xrandr <defunct> 1669 ? 00:00:00 sh <defunct> 1672 ? 00:00:00 cvt <defunct> 1717 ? 00:00:00 xrandr <defunct>
After I enable second virtual screen, it gets more:
ps -A | grep defu 1590 ? 00:00:00 xrandr <defunct> 1594 ? 00:00:00 sh <defunct> 1598 ? 00:00:00 cvt <defunct> 1628 ? 00:00:00 xrandr <defunct> 1669 ? 00:00:00 sh <defunct> 1672 ? 00:00:00 cvt <defunct> 1717 ? 00:00:00 xrandr <defunct> 2042 ? 00:00:00 sh <defunct> 2044 ? 00:00:00 cvt <defunct> 2054 ? 00:00:00 sh <defunct> 2057 ? 00:00:00 xrandr <defunct> 2074 ? 00:00:00 sh <defunct> 2076 ? 00:00:00 cvt <defunct> 2086 ? 00:00:00 sh <defunct> 2088 ? 00:00:00 cvt <defunct> 2099 ? 00:00:00 xrandr <defunct>
And, after I have moved & resized the virtual desktop windows, it grows further !
ps -A | grep defu 1590 ? 00:00:00 xrandr <defunct> 1594 ? 00:00:00 sh <defunct> 1598 ? 00:00:00 cvt <defunct> 1628 ? 00:00:00 xrandr <defunct> 1669 ? 00:00:00 sh <defunct> 1672 ? 00:00:00 cvt <defunct> 1717 ? 00:00:00 xrandr <defunct> 2042 ? 00:00:00 sh <defunct> 2044 ? 00:00:00 cvt <defunct> 2054 ? 00:00:00 sh <defunct> 2057 ? 00:00:00 xrandr <defunct> 2074 ? 00:00:00 sh <defunct> 2076 ? 00:00:00 cvt <defunct> 2086 ? 00:00:00 sh <defunct> 2088 ? 00:00:00 cvt <defunct> 2099 ? 00:00:00 xrandr <defunct> 2128 ? 00:00:00 sh <defunct> 2130 ? 00:00:00 sh <defunct> 2132 ? 00:00:00 cvt <defunct> 2143 ? 00:00:00 xrandr <defunct> 2160 ? 00:00:00 sh <defunct> 2162 ? 00:00:00 cvt <defunct> 2172 ? 00:00:00 sh <defunct> 2174 ? 00:00:00 cvt <defunct> 2185 ? 00:00:00 xrandr <defunct> 2202 ? 00:00:00 sh <defunct> 2204 ? 00:00:00 cvt <defunct> 2214 ? 00:00:00 sh <defunct> 2216 ? 00:00:00 cvt <defunct> 2227 ? 00:00:00 xrandr <defunct> 2260 ? 00:00:00 sh <defunct> 2262 ? 00:00:00 cvt <defunct> 2272 ? 00:00:00 sh <defunct> 2274 ? 00:00:00 cvt <defunct> 2285 ? 00:00:00 xrandr <defunct> 2304 ? 00:00:00 sh <defunct> 2306 ? 00:00:00 sh <defunct> 2308 ? 00:00:00 cvt <defunct> 2319 ? 00:00:00 xrandr <defunct> 2336 ? 00:00:00 sh <defunct> 2338 ? 00:00:00 sh <defunct> 2340 ? 00:00:00 cvt <defunct> 2351 ? 00:00:00 xrandr <defunct> 2370 ? 00:00:00 sh <defunct> 2372 ? 00:00:00 sh <defunct> 2374 ? 00:00:00 cvt <defunct> 2385 ? 00:00:00 xrandr <defunct> 2404 ? 00:00:00 sh <defunct> 2406 ? 00:00:00 cvt <defunct> 2416 ? 00:00:00 sh <defunct> 2418 ? 00:00:00 cvt <defunct> 2429 ? 00:00:00 xrandr <defunct>
comment:3 by , 4 years ago
This behavior is happening when Graphics Controller selected == VMSVGA.
I just tested and with VBoxSVGA - the one you get warning about that it's outdated and shouldn't be used - this behavior does NOT happen. No zombies. However, with VBoxSVGA second virtual monitor does not get enabled anymore ...
comment:4 by , 4 years ago
| Summary: | VBoxClient on Linux : leaves defunct zombies → VBoxClient on Linux : leaves defunct xrandr zombies |
|---|
comment:5 by , 4 years ago
| Guest type: | other → Linux |
|---|---|
| Host type: | other → all |
| Keywords: | vmsvga added |
comment:6 by , 4 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
follow-up: 11 comment:7 by , 4 years ago
Please attach the guest log. I need to know a few things like guest additions' version. And my educated guess is that this problem has been solved in the latest guest additions version. Please get them from our test builds download page and test again.
follow-up: 9 comment:8 by , 4 years ago
I cannot reproduce this xrandr defunct process issue anymore using the latest Trunc GA bits on OL6, OL8 and Fedora31 guests.
comment:9 by , 4 years ago
Replying to fbatschu:
I cannot reproduce this xrandr defunct process issue anymore using the latest Trunc GA bits on OL6, OL8 and Fedora31 guests.
The guest additions match the VirtualBox version I'm using this case - 6.1.6. My Linux Fedora is 30.
However I see VBox 6.1.8 was released, and I can try upgrading , including the guest additions.
comment:10 by , 4 years ago
Sorry for taking long to check 6.1.8.
I confirm I have nothing now I see with ps -A | grep defu. Or any xrandr for that matter. Thus the issue appears to have been fixed as of 6.1.8 - I installed both VBox and Guest updates.
comment:11 by , 4 years ago
Replying to gombara:
Please attach the guest log. I need to know a few things like guest additions' version. And my educated guess is that this problem has been solved in the latest guest additions version. Please get them from our test builds download page and test again.
Can I ask you, you asked for guest log, but in my Linux guest that log is always size 0. ->
0 -rw-------. 1 root root 0 Apr 27 13:19 VBox.log
The host log gets written (but that is Windows host log).
Where/how do I enable that guest log?
Forgot to set : Host is Win 10, Guest is Linux