Red Hat Bugzilla – Bug 468110
Kwin Compositing (OpenGL) + picture frame plasmoid = crashy, too many windows
Last modified: 2009-01-09 16:00:24 EST
Description of problem:
When OpenGL effects are enabled, and, my guess is, but I could be wrong, that one is using the picture frame plasmoid (mine is set to show a new image every 10 seconds), the KDE desktop jams up after a while, say, about 1 hour or so. It becomes impossible to open windows, dolphin will not open directories, or other strange effects. I notice that the dashboard looks normal, except that where the picture frame plasmoid is supposed to be, there is only a small, black diamond shape. What I do then is open a virtual terminal with the intention of trying to change the desktop effects = true to false on line 6 of kwinrc, but I cannot even log in on a virtual terminal. I see the login prompt, and when I enter my login name, the prompt disappears and a line is repeated 2 or 3 times. I believe it reads something like: there are too many windows open. The computer is unresponsive and I have no choice but to alt-SysRq-reisuo.
Version-Release number of selected component (if applicable):
Enable Desktop Effects (and enable the Picture Frame Plasmoid and set it to about 10 minutes). Use the computer for an hour or so. All of a sudden, when one is not expecting anything, nothing works anymore and the diamond shape appears where the picture frame plasmoid is supposed to be. The virtual terminal displays a message about too many windows.
Steps to Reproduce:
1.See How reproducible.
Dolphin barely opens directories anymore, it becomes impossible to open a window, not even the menu to select a program to run, etc.
Kwin OpenGL Desktop Effects should work. Whether there is an interaction between the Picture Frame Plasmoid (which opens a lot of windows in succession over a period of time) is just a guess. I have not tried using the computer without the picture frame. Perhaps I should, just to see?
I am using the onboard Intel graphics using xorg-x11-drv-i810-2.5.0-1.fc10.i386, but the problem existed for many previous versions of this driver. I didn't report for a long time, because kde-4.0 was rather buggy, and then the mesa and X servers were not yet mature, and finally the Intel graphic driver was not yet ready, but as of yesterday, the last piece has finally tumbled into completion with the release of intel driver 2.5 (however, even that is not truly ratified until kernel-2.29 when the kernel patches to allow modesetting are in place). Nevertheless, perhaps now is a good time to begin to initiate a resolution to this problem.
KWin compositing is still rather buggy, it's disabled by default for a reason. 4.2 will have some code to test whether compositing is actually working and enable it by default if the test passes, so we can only hope that it will be more reliable in 4.2. There's not much we can do to fix this stuff within Fedora, it needs to be fixed upstream.
In my experience, it's not kde that's buggy, but the compositing support in drivers. I'd venture this to be a hw/driver bug.
What video hw/driver is in use here?
Nevermind, I see intel in the comment now.
I can vouche that compositing was rock-solid for me (intel) with F-9/kde-4.1. F-10 has regressed quite a bit in that regard.
Ok. Just thought I'd bring it to attention. Yes, in F9, I used kde compositing without any problem. That's why I keep enabling it in F10, hoping that it will work. Then, I had this problem, was told it was DRI, then it was allegedly mesa, then it might have been the X server, and finally the intel driver, but as of yesterday, each of these components has finally given birth to a long-awaited update, so I thought...
To be clear, is it kwin or X dying? (From what I can tell the latter, which is what would likely point to a lower level issue)
I've got the same hw, and previously could reproduce the issue too, I'll update fresh, to confirm.
confirmed anti goodness, reassigning to i810 driver for some targetted love.
In the meantime, using XRender instead of OpenGL here seems to yield much better results for me.
Well, I really could not say, but, since I have a display and desktop, and am able to close, but not open windows, not even the menu, and I still have use of the mouse pointer to close those windows, and the keyboard obviously works, as I am able to switch to a virtual terminal and can type my login name (but cannot log in) and I am able to type alt-SysRq-sub, so I don't think X has died. It seems to be a kwin issue.
I have removed the picture frame plasmoid since reporting this and, so far, have not experienced the problem again, but that is not a sufficiently long test for me to be convinced. I had just thought that it was opening a new 'window' or picture every 10 seconds, so perhaps they were not getting properly closed, hence that strange message about too many windows being open and the desktop freezing up.
Yes, back in January, with the initial kde-4.0 release, OpenGL was not yet available, so I used XRender, but it was very slow and I ended up disabling effects as a result. I haven't given it another try yet, but will do so, if my test of not using the picture frame plasmoid proves fruitless.
OK, what I'm seeing is different than what are, I'll file separately.
Reassigning back to kdebase-workspace.
I don't know about my picture frame plasmoid theory. It happened again, and I have had it turned off sine yesteday.
I disabled OpenGL effects and am using XRender, now. Yuck! Is that ever slow and jumpy!
interesting... for me it's opengl that gets "yuck... slow", xrender isn't great, but it's better... for me anyway. ymmv.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
I think I am encountering this bug. When I am using Desktop Effects in KDE with the OpenGL compositing type (XRender doesn't have this problem) the system will eventually tell me that too many files are open and refuse to open any file (including programs) or even allow logins through a console. Wen that happens, killing xorg frees up enough so that I can at least reboot properly.
I have been retrying to see if it happens agian after KDE and xorg updates but so far nothing has fixed it. If I let the system run (not even interacting with it) once it starts using up files it eventually uses up all of them.
/proc/sys/fs/file-nr shows the number of open files rapidly rise even up to 180000+ out of about 200000 (I try not to let it get higher than that when testing because if I hit the limit, I lose all my unsaved files).
I am running Fedora 10 on a Lenovo Thinkpad T61 with Intel graphics. I don't have an xorg.conf file and can't think of anything else relevant I should post. Tell me if you need anything. I would like my OpenGL compositing back :)
Update: I have reported this bug to kde:
Thanks for reporting this upstream. Going to close this as UPSTREAM and we will monitor for resolution