https://bugs.kde.org/show_bug.cgi?id=398474

            Bug ID: 398474
           Summary: Kwin sometimes freezes, consuming 100% of one CPU core
           Product: kwin
           Version: 5.13.5
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kwin-bugs-n...@kde.org
          Reporter: kishor...@gmail.com
  Target Milestone: ---

Sometimes kwin freezes, and does not respond to mouse movement, keyboard
shortcuts etc. It usually happens when I am triggering the 'desktop grid'
effect via a screen corner, and the animation just stops halfway. However, I
cannot reporduce this consistently, and I am not sure if this is actually the
trigger. 

If I switch to a tty during such a freeze and open htop, I find that kwin_x11
is taking 100% of a CPU core. It does not respond to SIGTERM, so I usually have
to send SIGKILL and then start kwin again. 

I tried to capture to output of kwin during one such run (by starting kwin
using something like 'nohup kwin_x11 --replace > kwin_log_20180911-0915.txt &',
and it is below:

OpenGL vendor string:                   Intel Open Source Technology Center
OpenGL renderer string:                 Mesa DRI Intel(R) Haswell Mobile 
OpenGL version string:                  4.5 (Core Profile) Mesa 18.1.8
OpenGL shading language version string: 4.50
Driver:                                 Intel
GPU class:                              Haswell
OpenGL version:                         4.5
GLSL version:                           4.50
Mesa version:                           18.1.8
X server version:                       1.20.1
Linux kernel version:                   4.18.6
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
kwin_x11: ../libepoxy/src/dispatch_common.c:858: epoxy_get_proc_address:
Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.

After the last line, there is some stuff about raising a crash handler, which I
assume happens when I kill the process. 

I am runnning Arch Linux, and using the 'xf86-video-intel' driver. I am not
sure what other information would be relevant here.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to