| Summary: | KWIN hangs randomly with 100% CPU load | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Tomek <siedliszcze> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | siedliszcze |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 4.9.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Tomek
2012-11-27 17:51:00 UTC
how is that backtrace related to the "100 %" CPU load? Sounds/looks like OOM, probably eclipse is doing sth. "nasty" (like infinite show/hide or creating a HUUUUGE window to then shrink it down or similar nonsense. @Tomek can you please run "kdebugdialog" and ensure "kwin (1212)" is checked, then run "kwin --replace > ~/kwin.debug 2>&1" (from konsole) and try to cause the freeze. once frozen, move to VT1 as fast as possible, (login, maybe prepare a login) and run "gdb --pid=`pidof kwin` 2>&1 | tee ~/kwin.trace" Once gdb is done with it's lib loading, enter "bt" and then press enter until the entire stacktrace was printed. then enter "detach", then "quit", back in shell, run "export DISPLAY=:0 kwin --replace & sleep 5; exit". Then move back to VT7 to continue your work =) I managed to follow first of your suggestions and after freeze I got what i attach in pastebin: http://pastebin.com/P6ViYezr Unfortunately I wasn't quick enough to run "gdb --pid=`pidof kwin` 2>&1 | tee ~/kwin.trace" before kwin was restarted. After I move to VT1 I can see taht kwin uses 100% CPU and after some time i get message "Kernel out of memory" (or similar). After this message cpu load drops and after switching to VT7 it looks like kwin is restarting (window borders disappear, I can't swich between windows, but last active window is responsive) and after a while everything is back to normal. Is it possible, that I somehow run out of memory? I have 2GB RAM and 4 GB of SWAP, currently (10 minutes afrer crush) "free" reports: total used free shared buffers cached Mem: 2015 1814 201 0 61 362 -/+ buffers/cache: 1389 625 Swap: 4095 1391 2704 Total: 6111 3205 2905 OpenGL renderer string: Gallium 0.4 on NV84 kwin(6202) KWin::checkGLError: GL error ( PostPaint ): "GL_OUT_OF_MEMORY" nv50_screen_create:594 - nouveau_screen_init failed: -12 libGL error: failed to load driver: nouveau libGL error: Try again with LIBGL_DEBUG=verbose for more details. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x301) Either there's a leak in kwin texture usage or nouveau or the eclipse window demands exceptionally much memory. -> Can you try a) to cause this with the nvidia blob? b) (if yes) add a kwin rule to match the "eclipse" class and force the geometry to 1024x768? any update? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |