Version: KDE 3.4.0 Level "b" SUSE 9.3 X86_64 (using KDE KDE 3.4.0) Installed from: SuSE RPMs OS: Linux When using Konqueror, and not when using Firefox, I keep windows open for my common news sites and open/read/close new tabs for news items. Over several days, probably 10 days to a month, the X server grows from ~200Mb to 1.2Gb or more, at which point I lose the session... unless I log out in time and re-login. I have tried using Firefox instead (I prefer Konqueror), and found that the problem does not occur, or at least is #MUCH# less severe. Looking at the X server memory map in the /proc filesystem, there are numerous allocated memory areas consistent in number with the count of tabs closed on still open windows (sort of!). This may, of course, be an X bug, but as the effect seems to go away when I manage to desist from using Konqueror, I suspect a resource cleanup problem. I now have a dual amd x86_64 suse-9.3 2Gb Tyan based system. I had the same problem on previous smaller memory systems, with the difference that they locked up before I could log out and I had to kill the X session either by Ctrl-Alt-Backspace or in some cases by switching consoles etc. On 32-bit systems my recollection is that it took longer (1-2 months) for the X lockup to happen, but the symptoms were similar. Can anyone reproduce this problem ?
Does this problem still occur in KDE 3.5?
I have recently, i.e. last weekend 2006-09-04, acquired SuSE 10.1, which is based on KDE 3.5.1 (I think). I will report back when I have had a chance to establish whether there is any substantial difference between my existing SuSE 9.3, based on KDE 3.4.0 level "b" and the SuSE 10.1 installation.
Howard, any news on this bug?
I have just completed (earlier today) updating to SuSE 10.1 (finally!) and the difference so far is considerably for the better. Konqueror is now based on KDE 3.5.1 level "a". I won't know for several days how much of an improvement this is, but KDE Info Centre reports 22% Application Data resident vs about 80%+ previously, although I have since closed some of the session open web pages. In any case, much kudos to the KDE team! I will report again when I get a better feel for the improvement, and some time to check whether there is further work to do regarding VmRss in KDE System Guard.
Well, after a week, my X server has again reached 1.6Gb VmSize and 1.1Gb VmRss, after closing a few Konqueror windows. While I still think that SuSE 10.1 is an improvement over SuSE 9.3, there is still room for much improvement in memory usage, but the jury is still out on whether the X server or KDE in the form of Konqueror is the prime candidate for action required.
Having closed all bar one of my Konqueror windows, the X server has reduced down to a more reasonable 600 Mb, VmRss 165Mb. How did Konqueror manage to bloat the X server by 1000Mb ????? Either the X server needs to change, so that thrashing of that extra 1Gb to/from swap does not lock out all other display updates etc, or Konqueror needs to change to not overload X with so much resident memory load of images.
Thanks for investigating further. I'll retitle the bug to reflect your findings
I would like to comment some things. I got about 6 days running kde, with some trnsparent interruptions using suspend2. Today I noticed that the xserver process took 238MB virtual size and 107MB physical RAM. I got this results using xrestop(extract): res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 2000000 1682 126 1 2311 1535 57193K 79K 57272K 5793 xine - A Free Video Player - FAQ - Konqueror 2e00000 551 126 1 492 594 21206K 30K 21237K 5813 #debian.de paste zone - Konqueror 2200000 360 127 1 1578 945 20044K 34K 20079K 5794 rasasi - Konqueror 0e00000 971 127 1 2795 1246 14366K 55K 14422K 5935 Debugging WiFi LG #135 - Kontact Then I did some tests with the process 5813 which was the one I could close tabs in. In that konqueror instance I had 8 tabs, 2 of them were for file managing, not browsing. I closed all the tabs but one of the file managers. The total X resources went down from 21237K to 3030K and then I opened all the tabs again as they were and the X total resources for this process went up to 18053K. I'm not sure about how this things works, but I have been told about X server shouldn't store such amount of client data. Possibly, this is about khtml part because I think akregator part in kontact has same behaviour. KDE3.5.6, Xorg7.1, X driver i810, debian unstable.
I cannot keep a PC active form more than a day, so, could someone test if konqueror 3.5.9 and (or) konqueror 4 manage better the memory allocation?
No answers in two years. Timeout.