Out of curiosity:
Why use a QShardPointer and not directly allocate the object on the stack?
Would do the same.
On 05/23/2012 08:33 PM, Erik Hovland wrote:
Does the attached patch help at all?
E
On Wed, May 23, 2012 at 3:17 AM, Bart Cerneels<[email protected]> wrote:
Hey Gerald.
Thanks for the data you gathered. It certainly proves we have a
memleak problem. As you point out it's probably related to the
playlist, but that is not directly a give and likely is not the only
memleak there is.
I'll have a go finding it before the next release anyway.
I'm sharing this with the developer list.
On Wed, May 23, 2012 at 6:15 AM, Gerald B. Cox<[email protected]> wrote:
Just an FYI in case like me you leave amarok running at times... don't....
Amarok memory leak when changing tracks
https://bugs.kde.org/show_bug.cgi?id=298627
Easily reproducible - just load up a playlist and
select the repeat playlist option.
The only plugins I am using are mass
storage device and lastfm.
I ran the following command to document the leak:
top -b -d 150 -p 11866> amarok.txt
I then imported the results into a google spreadsheet you can view here:
http://goo.gl/Q4bZw
Memory utilization started out at 7.4% and ended up at 31.9% after approx 48
hours. The leak is steady and unrelenting. I ran the same playlist under QMMP
during the same period and memory utilization was steady at 2.5% throughout the
period.
_______________________________________________
Amarok-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/amarok-devel
