Description of problem: Looking for what is chewing up my memory -- I have 32GB installed. Version-Release number of selected component (if applicable): How reproducible: Dunno. Just discovered it. Steps to Reproduce: 1. Use the system is all I can say at this time. 2. 3. PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 28528 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28529 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.12 python /usr/share/mageiawelcome/mageiawelcome.py 28531 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:01.44 python /usr/share/mageiawelcome/mageiawelcome.py 28618 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28619 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28622 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28623 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28624 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28637 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28638 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28639 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28640 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28641 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28642 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py 28643 pfortin 1 0 3587M 54812 22376 S 0.0 0.2 0:00.00 python /usr/share/mageiawelcome/mageiawelcome.py Reproducible: Steps to Reproduce:
(In reply to Pierre Fortin from comment #0) > > How reproducible: Dunno. Just discovered it. > Please try whether the issue reoccurs after reboot. (If not: there wasn't a child or cat around who started MageiaWelcome many times?) If it happens again, without "helping" kids or pets: Which Desktop environment do you use? How long ago did you install Mageia 4? Since when did you notice something eats up the memory?
Keywords: (none) => NEEDINFOCC: (none) => marja11
(In reply to Marja van Waes from comment #1) > Please try whether the issue reoccurs after reboot. I've despised reboots since the original 4.77MHz IBM PC.... suggested no reboot upgrades should be possible circa 2000. I see this is coming with kpatch & kGraft... good enough hint about my feelings on reboot? :) > (If not: there wasn't a child or cat around who started MageiaWelcome many > times?) I live alone. > If it happens again, without "helping" kids or pets: > > Which Desktop environment do you use? KDE4 (part of mga4) > How long ago did you install Mageia 4? July 20, 2014. Last reboot was Thu Jan 8 13:12:53 EST 2015 Kernel 3.14.23-tmb-laptop-1.mga4 on an 8-processor x86_64 I keep the system up-to-date -- nightly cron pull of updates. > Since when did you notice something eats up the memory? Since at least mga2... I have reported various issues to kde, gnome, mageia, mozilla. My problem is that I feel like some issues cross boundaries between these various groups and I'm left with finger-pointing... Feel free to search bugs on these sites using my domain name as reporter/commenter. Below is orthogonal, I know... but to give you an idea what I struggle with... Been trying to get a handle on a bug(s) where strange problems creep in after at least 1 week when at 16GB, and only after about a month since upgrading to 32GB of main memory mid-January. Part of my trouble-shooting consists of capturing lsof output occasionally. These files vary from ~86K lines of output shortly after the last reboot to 278K lines. The most aggravating bug, when it kicks in (it did a few days ago), is this one: https://bugzilla.gnome.org/show_bug.cgi?id=724200 https://bugs.kde.org/show_bug.cgi?id=331017 https://bugs.mageia.org/show_bug.cgi?id=12101 which may be related to: https://bugs.kde.org/show_bug.cgi?id=338332 because both occur about the same time (~1 week on 16GB; ~1 month on 32GB)... Noticed another potential memory leak; but the only tool I'm currently aware of is valgrind; but _it_ has to start the suspect application... If there's another tool which can attach to a PID (like gdb) and check memory allocations, it would help greatly right now... Until someone with more code familiarity than me, and full access to the bug databases, does an analysis of how many bugs [appear to] relate to memory issues, things can only become more difficult to debug over time.... Sorry for semi-ranting... :)
seems resolved in mga5
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED