Summary: | Plasma crash because X makes memory overflow slowly in few hours | ||
---|---|---|---|
Product: | [Applications] knemo | Reporter: | dilnix <dilnix> |
Component: | general | Assignee: | John Stamp <jstamp> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | dilnix, mbriza, nucleo, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=819517 | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
broken textures google-chrome Broken textures at all (google-chrome & akregator) This is what krunner shows on fresh startes system This is what krunner shows on 1 hour after some strange changes. After 10 hours after fresh start and 1-2 hours before crash. the last knemorc file that been used |
Description
dilnix
2012-05-06 16:54:17 UTC
Crash is repeated only after reboot... if not then is no repeating after reloading Plasma... by now... I tried to wait 8 hours with my pc is standby, and no repeat. Crash has repeated after 22 hours after previous without any rebooting/relogging in... But now kwin has not been reloaded, so all looks ugly & made hard reset... Created attachment 70959 [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:
Just watched how my PC lagging while X eating 30% CPU & launched only Gmail in Google-chrome... That lagging lasted 2-3 hours before crash...
-- Backtrace (Reduced):
#8 0x42a8ca91 in QGraphicsWidget::~QGraphicsWidget (this=0xc1bd3a0, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:272
#9 0x42a8cce3 in QGraphicsWidget::~QGraphicsWidget (this=0xc1bd3a0, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:277
#10 0x42a32b60 in QGraphicsItem::~QGraphicsItem (this=0xc1b8fe0, __in_chrg=<optimized out>) at graphicsview/qgraphicsitem.cpp:1493
#11 0x42a8cb1f in ~QGraphicsObject (this=<optimized out>, __in_chrg=<optimized out>) at ../../src/gui/graphicsview/qgraphicsitem.h:547
#12 QGraphicsWidget::~QGraphicsWidget (this=0xc1b8fd8, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:232
Also reported in RH Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=819517 Created attachment 71123 [details]
broken textures google-chrome
As i said, no matter of been system rebooted or not, crash is repeating always in KDE. In some 10-12 hours.
For some few hours before crash system begining to be slow. Google-chrome & other programs has a broken interface (attaching screenshots for this). CPU usage is 30-40% by X process. Memory & swap slowly fills more and more (attaching more screenshots for this). If I leave computer working and go to sleep so see broken unstable KDE at morning. I meen - no windows, no tabs, no plasma, only some error message without WM (kwin) and just hot wind from CPU cooler, so i can't do anything but hard reset.
Attaching more files.
Created attachment 71124 [details]
Broken textures at all (google-chrome & akregator)
This and previous screenshot is about 2-3 hours before plasma crash. I don't know what is going on... what the action changes the situation to this. Because before this all system works fine, CPU runs on 5-12%, programs has no broken textures in workspace...
Created attachment 71125 [details]
This is what krunner shows on fresh startes system
Created attachment 71126 [details]
This is what krunner shows on 1 hour after some strange changes. After 10 hours after fresh start and 1-2 hours before crash.
I don't know what is that...
Forgot some note... When this strange action lasts and google-crome (and almost any app) has broken textures inside workspace, firefox has no any problem. It has no broken textures inside workspace and I can use it forward before memory overfills and KDE crashes. See also: https://bugzilla.redhat.com/show_bug.cgi?id=819517 I launched that report too... and posted some new info in there 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 =) OK, triaging to knemo component That seems odd. Would you please attach your knemorc file? Also, what version of KNemo are you using? Hrm, seems fedora's pkg maintainer built knemo with -DLEGACY_TRAY_ICON=true to workaround bug #226650 (which has since been fixed for quite awhile). I bet that may be contributing to the problem. Created attachment 72417 [details] the last knemorc file that been used Included knemorc file... But listen, it's not old file... I just made fresh install of my system few days ago and now it is Fedora 17 x86_64. So i can't tell you what a version of knemo i was used before reinstalling. But in fresh system it was some 0.7.x version. Don't remember what version exactly because i removed fully it 2 days ago (when found problem). But official repos offers 0.7.3-1 now... Yes, i can try version you offered (http://koji.fedoraproject.org/koji/taskinfo?taskID=4228559)... But only if you tell me how to use it. Because i see that it is SRC version of rpm package. (In reply to comment #14) > Hrm, seems fedora's pkg maintainer built knemo with > -DLEGACY_TRAY_ICON=true > to workaround bug #226650 (which has since been fixed for quite awhile). I > bet that may be contributing to the problem. When KNemo window opened from tray it still can appear on background of other windows without -DLEGACY_TRAY_ICON=true. And I saw such behavior also for other apps. (In reply to comment #14) > Hrm, seems fedora's pkg maintainer built knemo with > -DLEGACY_TRAY_ICON=true > to workaround bug #226650 (which has since been fixed for quite awhile). I > bet that may be contributing to the problem. Is it (http://kojipkgs.fedoraproject.org//work/tasks/8560/4228560/knemo-0.7.3-1.fc17.1.x86_64.rpm) package that you meen me to try? that's the one (assuming you're on a x86_64 box) I just tried this package... 25 hours gone and no same problems found... only 1 time - there was Segmentation Fault (11) by Plasma-desktop... on 20 hour of standby... Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug. |