Notifications plasmoid, leak?

[Dave Lepore]

I can reproduce it in trunk updated and compiled a couple of hours ago. Also, 
the issue is not reproducible in trunk compiled the 24th of may, so the cause  
should be a commit in this period of time.

Hope this helps.
Dave.

On Sunday 06 June 2010 12:30:34 Marco Martin wrote:
> On Sunday 06 June 2010, Alex Fiestas wrote:
> > Hi fellows
> > 
> > Seems that the notifications plasmoid is leaking X11 memory for each
> > notification
> > 
> > How to reproduce:
> > 1-Execute system activity (Ctrl+Esc), and show the X11 memory column
> > 2-Remove your notifications plasmoid inside plasma.
> > 3-Execute "plasmoidviewer notifications"
> > 4-Execute "kdialog --passivepopup foo" to add a notification.
> > 
> > when adding notifications take a look at the X11 Memory column, you'll
> > see how it increases 400K per each notification but only decrease 100
> > when the notification is closed.
> > 
> > I thought it would be because the notification is saved in the
> > Notifications browser but:
> > 1-Click on the plasmoid so the notification browser is shown
> > 2-Close one notification when looking at the X11 Memory
> > 
> > You should see how the X11 memory INCREASE each time you close a
> > notification. Additionally when you close the entire browser, the memory
> > is not released.
> 
> trunk?
> when is updted?