| Summary: | Plasma Desktop crashes after several hours (due to memory leak of plasmoid) | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | happy <hh.kde.crash> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | ahartmetz, boutilpj, cfeck, denis.kot, dilnix, dlott+kde, franklin, gasortega, generatorglukoff, jjasen, jwjstone, pahan, spb.nevill, teedub303 |
| Priority: | NOR | ||
| Version: | 4.8.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
information about the crash
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
happy
2012-03-21 01:58:21 UTC
One of your plasma widgets has a memory leak. Try to find out which by removing one of them. On Wed, 21 Mar 2012 02:34:42 AM you wrote:
> One of your plasma widgets has a memory leak. Try to find out which by removing
> one of them.
fair enough... thanks for the quick reply.
I would add that my widget set didn't change from pre 4.8.0 either - pretty minimal:
- one folder view (desktop folder)
- one note
- three icons
- analogue clock
- system load viewer
- hardware temperature
- network activity
(all out of the standard set of widgets)
I've never done any work with desktop widgets.
What do you think of these assumptions:
(1) the icons and the note are probably not leaking.
(2) that any leak is because of some activity
(3) that the more activity, the more likely the leak (like the network or the temperature).
Is there some method or tool I can use to monitor the resource usage of an individual widget?
I'm happy to do trial-and-error but that could take a while.
cheers,
d
Created attachment 69918 [details]
information about the crash
Sorry, not used to the tracker yet. Application: plasma-desktop KDE Platform Version: 4.8.00 Operating System: 3.2.0-20-generic Distribution: Kubuntu 12.04 I may have been affected with the same error. I was away from the laptop when it happened, though. It had crashed before with sympthoms similar to what happy described (wrong widget background). The only widgets I have installed that were not on in Kubuntu 12.04 by default were System Monitor and Icon Tabs. Haven't worked all the way through the set of applets running individually but can't reproduce it yet. The System Load viewer (not yet tested) is looking likely - temperature and network activity don't appear to be the cause. *** Bug 297011 has been marked as a duplicate of this bug. *** *** Bug 297514 has been marked as a duplicate of this bug. *** Created attachment 70178 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1
- What I was doing when the application crashed:
Nothing. I left the laptop running for a few hows. Only psi+, chromium, and one instance of Konsole were launched.
-- Backtrace (Reduced):
#6 0x00007f26ae1d1445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f26ae1d4bab in __GI_abort () at abort.c:91
[...]
#12 0x00007f26ab42f16c in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f26ab433f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x00007f26ae599a13 in kdemain (argc=1, argv=0x7fff161ab418) at ../../../../plasma/desktop/shell/main.cpp:120
Created attachment 70289 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
- What I was doing when the application crashed:
Left KTorrent to run for a few hours. There was no user interation until the crash.
-- Backtrace (Reduced):
#6 0x00007f42125d2445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f42125d5bab in __GI_abort () at abort.c:91
[...]
#12 0x00007f420f83016c in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f420f834f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x00007f421299aa13 in kdemain (argc=1, argv=0x7fff7aa3d468) at ../../../../plasma/desktop/shell/main.cpp:120
Created attachment 70489 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
- What I was doing when the application crashed:
Nothing. Returned to desktop after computer was idle for about 8 hours.
-- Backtrace (Reduced):
#6 0x0000003dfc436285 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x0000003dfc437b9b in __GI_abort () at abort.c:91
#8 0x000000383dabbc5d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x000000383dab9e16 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x000000383dab9e43 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
*** Bug 297237 has been marked as a duplicate of this bug. *** *** Bug 298213 has been marked as a duplicate of this bug. *** Created attachment 70625 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
- What I was doing when the application crashed:
I left the computer running and walked away. This has happened several times now.
-- Backtrace (Reduced):
#6 0x000000388f036285 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x000000388f037b9b in __GI_abort () at abort.c:91
#8 0x00000038924bbf8d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x00000038924ba146 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x00000038924ba173 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
(In reply to comment #10) > Created attachment 70489 [details] > New crash information added by DrKonqi > > plasma-desktop (0.4) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 > > - What I was doing when the application crashed: > > Nothing. Returned to desktop after computer was idle for about 8 hours. > > -- Backtrace (Reduced): > #6 0x0000003dfc436285 in __GI_raise (sig=6) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #7 0x0000003dfc437b9b in __GI_abort () at abort.c:91 > #8 0x000000383dabbc5d in __gnu_cxx::__verbose_terminate_handler () at > ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 > #9 0x000000383dab9e16 in __cxxabiv1::__terminate (handler=<optimized out>) > at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40 > #10 0x000000383dab9e43 in std::terminate () at > ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50 I upgraded my laptop to Fedora 17 Beta two weeks ago and have not had the problem since. Used to happen on a daily basis. Qt: 4.8.1 KDE: 4.8.3 Created attachment 71017 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
nothing. just unlock screensaver when came to work.
-- Backtrace (Reduced):
#6 0x00007f14cd4fa445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f14cd4fdbab in __GI_abort () at abort.c:91
[...]
#12 0x00007f14ca75716c in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f14ca75bf67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x00007f14cd8c2a13 in kdemain (argc=1, argv=0x7fffdce37ae8) at ../../../../plasma/desktop/shell/main.cpp:120
*** Bug 299750 has been marked as a duplicate of this bug. *** *** Bug 300696 has been marked as a duplicate of this bug. *** *** Bug 299255 has been marked as a duplicate of this bug. *** Confirmed by duplicates. *** Bug 302992 has been marked as a duplicate of this bug. *** (In reply to comment #1) > One of your plasma widgets has a memory leak. Try to find out which by > removing one of them. In my case, if I removed all the widgets and left an empty plasma desktop, it wouldn't crash. Then I tried to add a standard panel back (with task manager, system tray, digital clock), it crashed after some time. Now I'm testing with an empty panel only. Current status: The plasmoid that caused plasma-desktop crashed seemed to be system tray on a panel. I restarted a standard panel and removed system tray, it didn't crash so far. If I started an empty panel and add system tray into it, no any other plasmoids, it would crash. Later I'll try if I put the system tray on the desktop instead of panel. But I wonder if anyone would have the same symptom as mine. I found a source of problem... It was knemo... i just removed it fully (yum remove knemo) and restarted system... now have no problem during 24 hours online =) Thanks for the investigation. Now it would be interesting to find out which widget or application in the system tray causes the issue. For example, try removing mixer applet or update notifiers, or whatever else is hidden there. (In reply to comment #24) > Thanks for the investigation. Now it would be interesting to find out which > widget or application in the system tray causes the issue. For example, try > removing mixer applet or update notifiers, or whatever else is hidden there. Here's a possible root cause: the nepomuk indexing. If the nepomuk file indexer was disabled, it wouldn't crash. I've been testing it for at least two hours and am still testing it. I also disabled printer applet, korganizer reminder and akonaditray, but nepomuk file indexer is the most possible root cause because it also explains why my desktop PC wouldn't crash like that in my laptop. Seem to share the problem. Interesting info from top: 9124 dan 20 0 2092m 389m 62m T 0.0 2.4 19:02.97 /usr/bin/plasma-desktop 9132 dan 20 0 2092m 389m 62m T 0.0 2.4 0:01.49 /usr/bin/plasma-desktop 9133 dan 20 0 2092m 389m 62m T 0.0 2.4 0:01.50 /usr/bin/plasma-desktop 9134 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.00 /usr/bin/plasma-desktop 2732 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.04 /usr/bin/plasma-desktop 2733 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.08 /usr/bin/plasma-desktop 2734 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.07 /usr/bin/plasma-desktop 2735 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.00 /usr/bin/plasma-desktop 2736 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.05 /usr/bin/plasma-desktop 2737 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.07 /usr/bin/plasma-desktop 2738 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.04 /usr/bin/plasma-desktop 2739 dan 20 0 2092m 389m 62m T 0.0 2.4 0:00.00 /usr/bin/plasma-desktop Backtrace of the crash I experienced: Application: Plasma Desktop Shell (plasma-desktop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd8fe9b3780 (LWP 9124))] Thread 12 (Thread 0x7fd8de2f7700 (LWP 9132)): #0 0x00007fd8fe2908bd in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd8f247b8cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fd8f2440ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd8f2440fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fd8f2441164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fd8fb463426 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007fd8fb432c82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8fb432ed7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fd8fb331fa7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fd8fb4129ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #13 0x0000000000000000 in ?? () Thread 11 (Thread 0x7fd8dd124700 (LWP 9133)): #0 0x00007fd8fe2ab904 in pthread_mutex_unlock () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd8f247c5d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fd8f2440f4e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd8f2441164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fd8fb463426 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007fd8fb432c82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007fd8fb432ed7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8fb331fa7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fd8fb4129ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #12 0x0000000000000000 in ?? () Thread 10 (Thread 0x7fd8dc923700 (LWP 9134)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8f8217222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007fd8f8217259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x0000000000000000 in ?? () Thread 9 (Thread 0x7fd8c4405700 (LWP 2732)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 8 (Thread 0x7fd8b9327700 (LWP 2733)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee29f4 in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #7 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000000000 in ?? () Thread 7 (Thread 0x7fd8b3fff700 (LWP 2734)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee29f4 in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #7 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000000000 in ?? () Thread 6 (Thread 0x7fd8b8b26700 (LWP 2735)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 5 (Thread 0x7fd8b37fe700 (LWP 2736)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee29f4 in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee29f4 in ?? () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #7 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #8 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x0000000000000000 in ?? () Thread 4 (Thread 0x7fd8b25b5700 (LWP 2737)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 3 (Thread 0x7fd8b1db4700 (LWP 2738)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 2 (Thread 0x7fd8b15b3700 (LWP 2739)): #0 0x00007fd8f2d49d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd8fb3354db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fd8f6ee00eb in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x00007fd8f6ee29db in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x00007fd8f6ee184f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x00007fd8f6ee18db in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x00007fd8fb334fcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fd8f2d45e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fd8fe29dcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fd8fe9b3780 (LWP 9124)): [KCrash Handler] #6 0x00007fd8fe1e0425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007fd8fe1e3b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x00007fd8fa3a269d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007fd8fa3a0846 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00007fd8fa3a0873 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x00007fd8fa3a09b6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x00007fd8fb43316c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x00007fd8fb437f67 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x00007fd8fe5aaa13 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so #15 0x00007fd8fe1cb76d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #16 0x0000000000400671 in _start () I've seen it happen with a bare panel (when I had just installed). Has anyone come up with a fix? Hello everyone I found at least one possible way to reproduce this bug: 1. I use psi-im as messenger 2. On every new message, it flash icon in system tray 3. On KDE 4.9.3 it produce X11 memory leaks from plasma-desktop at rate around 50Kb/sec (I've measured from ksysguard) So I've bisected at found that offending commit is: commit ae04d14bd4977225787169adb88d88da7a19de74 Author: Luboš Luňák <l.lunak@suse.cz> Date: Wed Oct 5 12:25:28 2011 +0200 less Xlib code, force Qt to use X pixmap for QPixmap instead REVIEW: 102770 I've reviewed that commit and have made a patch, that works for me: diff --git a/plasma/generic/applets/systemtray/protocols/fdo/x11embedcontainer.cpp b/plasma/generic/applets/systemtray/protocols/fdo/x11embedcontainer.cpp index 1826512..eabea6a 100644 --- a/plasma/generic/applets/systemtray/protocols/fdo/x11embedcontainer.cpp +++ b/plasma/generic/applets/systemtray/protocols/fdo/x11embedcontainer.cpp @@ -236,7 +236,7 @@ QPixmap X11EmbedContainer::toX11Pixmap(const QPixmap& pix) return pix; Pixmap xpix = XCreatePixmap(pix.x11Info().display(), RootWindow(pix.x11Info().display(), pix.x11Info().screen()), pix.width(), pix.height(), QX11Info::appDepth()); - QPixmap wrk = QPixmap::fromX11Pixmap(xpix); + QPixmap wrk = QPixmap::fromX11Pixmap(xpix, QPixmap::ExplicitlyShared); QPainter paint(&wrk); paint.drawPixmap(0, 0, pix); paint.end(); Can someone else also review/confirm this? Thanks, Andrey (In reply to comment #27) > I found at least one possible way to reproduce this bug: > 1. I use psi-im as messenger > 2. On every new message, it flash icon in system tray > 3. On KDE 4.9.3 it produce X11 memory leaks from plasma-desktop at rate > around 50Kb/sec (I've measured from ksysguard) > less Xlib code, force Qt to use X pixmap for QPixmap instead I found the same problem with using latest Skype in Fedora 18 x64. Process X is slowly growing in memory usage (200 Mb and more) and makes memory leak during maximum 6 hours. When starting system without Skype - there no problem - uptime 32 hours, process X amounts 32-64 Mb memory. Is anybody can fix this problem? Because Skype community is silent as dead... Looks like another duplicate of the tray code leaking X pixmaps. *** This bug has been marked as a duplicate of bug 314919 *** |