Bug 26080

Summary: Continiously dbus-daemon memory usage increase.
Product: dbus Reporter: Dmitriy Styazhkin <maroldorn>
Component: coreAssignee: Havoc Pennington <hp>
Status: RESOLVED WORKSFORME QA Contact: John (J5) Palmieri <johnp>
Severity: normal    
Priority: medium Keywords: NEEDINFO
Version: 1.2.x   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Dmitriy Styazhkin 2010-01-17 07:25:51 UTC 
I faced with dbus-daemon memory leak problem, when I made some customization of superkaramba widget. In few word, I added an Amarok playback monitoring by providing to me output of next command, which is constantly implementing, with short interval:

artist=`qdbus org.kde.amarok /Player GetMetadata | grep -m1 artist: | cut -c 9- | sed -e 's/.*/\U&/'`;[ `echo $artist | wc -c` -lt 27 ] && echo $artist || echo `echo $artist | cut -c -19`...

title=`qdbus org.kde.amarok /Player GetMetadata | grep -m1 title: | cut -c 7- | sed -e 's/^[ \t]*//'`;[ `echo $title |  wc -c` -lt 25 ] && echo $title || echo `echo $title | cut -c -19`...

album=`qdbus org.kde.amarok /Player GetMetadata | grep -m1 album: | cut -c 7- | sed -e 's/^[ \t]*//'`;[ `echo $album |  wc -c` -lt 25 ] && echo $album || echo `echo $album | cut -c -19`...

Then I found that it cause endless raise of dbus-daemon memory usage. I stop usage of this widget, but I think, that it's bug. I've attached this widget to the report.
Comment 1 Simon McVittie 2011-02-07 01:50:14 UTC 
(In reply to comment #0)
> I've attached this widget to the report.

You haven't; could you correct that, please? :-)

Is this still reproducible with the latest version (dbus 1.4.1, or a later commit from the dbus-1.4 branch in git)?

(If the widget performs those commands in a tight loop with no delay, then it'll hog your CPU, so you wouldn't want to use it anyway.)
Comment 2 Simon McVittie 2013-08-27 16:34:49 UTC 
No more info provided. WORKSFORME.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.