high cpu use after x11 updates

[Niclas Zeising]

On 2019-06-17 01:17, AN wrote:
> Hi:
> 
> FreeBSD FBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #93 r349104: Sun Jun 
> 16 08:41:26 EDT 2019 
> root at FBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL  amd64 1300031
> 
> After recent updates to several x11 ports, the process /usr/local/bin/X 
> seems to be using a lot of cpu resources.  Historically I seem to 
> remember X using something less than 1% cpu on this machine.  Here are 
> the related ports that were updated recently:
> 
>      + x11/libxshmfence (libxshmfence-1.2_4 -> libxshmfence-1.3)
>      + x11/libXext (libXext-1.3.3_3,1 -> libXext-1.3.4,1)
>      + x11/libXdamage (libXdamage-1.1.4_5 -> libXdamage-1.1.5)
>      + x11/libXcursor (libXcursor-1.1.15_2 -> libXcursor-1.2.0)
>      + x11-toolkits/libXmu (libXmu-1.1.2_5,1 -> libXmu-1.1.3,1)
>      + x11/libXrandr (libXrandr-1.5.1_2 -> libXrandr-1.5.2)
>      + x11/libXvMC (libXvMC-1.0.10_2 -> libXvMC-1.0.11)
>      + x11/sessreg (sessreg-1.1.1 -> sessreg-1.1.2)
>      + x11/libxkbfile (libxkbfile-1.0.9_2 -> libxkbfile-1.1.0)
>      + x11/xkeyboard-config (xkeyboard-config-2.24_1 ->
>          xkeyboard-config-2.27)
>      + x11/libxkbcommon (libxkbcommon-0.8.0_1 -> libxkbcommon-0.8.4)
>      + x11/libXxf86dga (libXxf86dga-1.1.4_5 -> libXxf86dga-1.1.5)
>      + x11/libXcomposite (libXcomposite-0.4.4_5,1 ->
>          libXcomposite-0.4.5,1)
> 
> I rebuilt the xserver and am still seeing the same behavior.  Are there 
> any other ports I need to rebuild?  What other info can I provide?  Any 
> suggestions would be appreciated.
> 
> Also, I am using:
> nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX 
> platforms  390.87  Tue Aug 21 15:53:31 PDT 2018
> nvidia0: <GeForce GT 710> on vgapci0
> and running compiz.
> 
> 
>  From top:
> 21865 root         21   -1  6528M   300M select   4  28:35   6.55% 
> /usr/local/bin/X :0 -auth /root/.serverauth.199
> 
> Thanks in advance for any advice.

Hi!
is you update just the ports, or also the base system at the same time?
Any chance you can try to undo either the ports update or the base 
system update, and see if the problem persists?
Regards
-- 
Niclas