Public bug reported:

After some uptime, xfwm4 is VERY slow at something, to the point that
it's consuming 100% of CPU on a Xeon system and making the system
entirely unusable. I don't know who is leaking what, but somebody is
clearly leaking something.

I don't have debug symbols, so this is the best I can get:

Thread 1 (Thread 0x7f7b9d98af00 (LWP 27599)):
#0  0x00007f7b9f1e8b7f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#1  0x00007f7b9f1e8be2 in gdk_x11_display_error_trap_push () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2  0x0000555c9582c771 in ?? ()
#3  0x00007f7b9ee75248 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f7b9ee7471e in g_main_context_dispatch () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f7b9ee74ad0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f7b9ee74dc3 in g_main_loop_run () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f7b9f4d2c2d in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x0000555c958222ce in ?? ()
#9  0x00007f7b9e7861e3 in __libc_start_main (main=0x555c95821b50, argc=6, 
argv=0x7fffbeb91c18, init=<optimized out>, fini=<optimized out>, 
rtld_fini=<optimized out>, stack_end=0x7fffbeb91c08) at ../csu/libc-start.c:308
#10 0x0000555c9582249e in ?? ()


or

Thread 1 (Thread 0x7f7b9d98af00 (LWP 27599)):
#0  0x00007f7b9f1e8b83 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#1  0x00007f7b9f1e8be2 in gdk_x11_display_error_trap_push () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2  0x0000555c9582e33a in ?? ()
#3  0x0000555c95834f1b in ?? ()
#4  0x0000555c958337d0 in ?? ()
#5  0x00007f7b9f1f0f4f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#6  0x00007f7b9f1f133a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#7  0x00007f7b9f1b9094 in gdk_display_get_event () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#8  0x00007f7b9f1f0fe6 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9  0x00007f7b9ee7484d in g_main_context_dispatch () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f7b9ee74ad0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f7b9ee74dc3 in g_main_loop_run () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f7b9f4d2c2d in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#13 0x0000555c958222ce in ?? ()
#14 0x00007f7b9e7861e3 in __libc_start_main (main=0x555c95821b50, argc=6, 
argv=0x7fffbeb91c18, init=<optimized out>, fini=<optimized out>, 
rtld_fini=<optimized out>, stack_end=0x7fffbeb91c08) at ../csu/libc-start.c:308
#15 0x0000555c9582249e in ?? ()

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xfwm4 4.14.0-1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Feb 24 23:18:34 2020
InstallationDate: Installed on 2019-01-21 (399 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: xfwm4
UpgradeStatus: Upgraded to eoan on 2019-11-10 (106 days ago)

** Affects: xfwm4 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864613

Title:
  xfwm4 very, very slow - leaking something?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1864613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to