|
Bugzilla – Full Text Bug Listing |
| Summary: | Memory leak | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | John Doe <omgwtfvroom> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.2 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
testcase
Window showing SYSINFO Window showing SYSINFO |
||
|
Description
John Doe
2007-06-08 23:39:42 UTC
I can verify on 3 different v10.2 machines on my local LAN that this occurs. I never noticed it before but it does explain a couple of unexplained and unwanted logins, or re-logins that happened when I was using a lot of system memory and opened a sysinfo window and refreshed it a couple of times to see if a drive still had enough space and bam...I was logged out and presented with a login screen and all of my running programs were killed in the process. This has happened both before and after I upgraded KDE to the latest available version. Verified with Konqueror 3.5.5 on OpenSuSE 10.2 . You have to refresh it quite often (e.g. twice a sec) to be able to see it. top shows growing usage of VIRT, but xrestop doesn't show any significant change -> looks like X bug. Also, I can only reproduce this problem only on testing machine with ATI card (radeon driver) but not on my primary machine with nVidia card (nvidia driver), I'm not sure if it's relevant. I tried "sysinfo:/" in konqueror
--> Protocol not supported
sysinfo
How can one reproduce this issue?
Created attachment 146275 [details]
testcase
It is part of kdebase3-SuSE, normally installed with KDE. This testcase however reproduces the problem as well (run repeatedly).
Created attachment 146279 [details]
Window showing SYSINFO
Created attachment 146280 [details]
Window showing SYSINFO
On my desktop is an icon called 'My Computer', installed when my user was created. As you can see, when that icon is launched, a window is launched in konqueror pointing to sysinfo:/ showing the state of my system. By hitting the refresh icon in the window and observing the amount of memory displayed, you will see it decrease. In my system when I am running large number of programs in other desktops, I can apparantly run out of memory doing this and I find myself being logged out and all running processes killed and I am presented with another login session which starts with my full complement of memory. None of my previous programs are running but any that are normally started at login will be restarted. This happens on all of my machines which currently are all at 10.2 and running 3.5.7 (I believe it is) KDE. Previously I had no idea why I was occasionally being logged off until the original poster mentioned the bug and I tested it and found myself being logged out suddenly after a while of noticing the decreasing memory. I don't know if the memory loss is caused by KDE, sysinfo, X or whereever, I can only 'see' it as described and feel its effects as noted. Richard I bet this doesn't happen on machines, which enabled DRI (same applies to machines, which use NVIDIA driver). This would be another duplicate of Bug #211314. This issue has been fixed for openSUSE 10.3 (Mesa update). Workaround for 10.2: Enable DRI. (add ' Load "dri" to section "Module" of /etc/X11/xorg.conf). (In reply to comment #9) > I bet this doesn't happen on machines, which enabled DRI (same applies to > machines, which use NVIDIA driver). This would be another duplicate of Bug > #211314. This issue has been fixed for openSUSE 10.3 (Mesa update). Workaround > for 10.2: Enable DRI. (add ' Load "dri" to section "Module" of > /etc/X11/xorg.conf). > I applied the patch as you suggested to the /etc/X11/xorg.conf and logged out (did not reboot machine) and upon relogging in, I tested the sysinfo refresh repeatedly with NO apparant memory leak. Thus, your hunch appears to be on track. At least you now know where to look to actually fix it for everyone. Thanks. *** This bug has been marked as a duplicate of bug 211314 *** |