Summary: | kwin crashes with intel_do_flush_locked failed: No space left on device | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Orion Poplawski <orion> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | detlev.casanova, kdebugs |
Priority: | NOR | ||
Version: | 4.8.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Orion Poplawski
2012-09-24 21:19:53 UTC
Do you get a backtrace (DrKonqui dialog showing up, click on "developer information") It btw. would be entirely the drivers fault. Even if we somewhere exceeded the pbuffer or vbo limits, we should simply get a GL error and you a blck window - but no way a crash. According to google, this error btw. happens to everybody (remains the question whether it's actually related to the crash -> backtrace ;-) We do not get a backtrace. I've disabled compositing for now. could you gdb attach kwin, cause / wait for the crash and obtain the trace from gdb? I'm also experiencing this crash and will try to. (KDE 4.9.3) This crash has also been reported to the Debian BTS in August: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686157 Apparently, kwin does not really "crash" but catches an invalid condition / state and exits manually with a failure code, which also explains that Dr. Konqui does not kick in: (gdb) continue Continuing. [Thread 0x7f02dd95e700 (LWP 17132) exited] [Thread 0x7f02cd535700 (LWP 17143) exited] [Thread 0x7f02f8e9e780 (LWP 17128) exited] [Inferior 1 (process 17128) exited with code 01] (gdb) The program is not being run. (gdb) bt full No stack. (gdb) Any hints on how to diagnose that and how to get the desired backtrace? Is there any method I should / could place a breakpoint at? (I'm pretty inexperienced with gdb and kwin's / KDE's internals, so please, if possible, provide sufficient details for me to be able to follow.) BTW, it looks as if the crash could be triggered, or at least the likelyhood of the crash can be increased, by opening quite a few windows and then task-switching between them using cover flow. 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) That's a SIGCHLD - have you tried switching between SNA & UXA? Tagging upstream - that thing crashes everything and kwin cannot prevent SIGCHLDs (but pot. catch and restart on them) Also the problem is reported for compiz ("unity") and mutter (gnome3) *** Bug 317267 has been marked as a duplicate of this bug. *** |