Re: Memory leak? in classic and maybe in ng

Hello,

On 3/22/06, Tomi Luhtala <tomi.luhtala-Eaijstg/Es0AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:

I wonder where or when the SystrayPopupWindow instance is destroyed?

I'm afraid it's never destroyed :-(.

The code can be found in class Systray::setCallIncoming

 

Code snipped:

 

      SystrayPopupWindow * popup = new SystrayPopupWindow();

      popup->setTitle(text);

      popup->setContact(phoneNumber, contact);

 

where the popup is freed?

It's freed when the application quit, which is not something we want since many SystrayPopupWindows can be instantiated during the application lifetime.  It seems that there can be several solutions to this problem.

One would be to keep a reference to this SystrayPopupWindow somewhere else and reuse it if it's not null, or delete it and recreate one. Another solution would be to set the "DeleteOnClose" attribute and call the close method instead of hide in SystrayPopupWindow's implementation when timeout is reached.

Ticket #406 has been created to track this issue.

Thank you very much for this insightful report, and sorry for the late answer.

Regards,

-- 
Julien Gilli
_______________________________________________
Wengophone-devel mailing list
Wengophone-devel-ZwoEplunGu1JKUZHOYzk1kEOCMrvLtNR@xxxxxxxxxxxxxxxx
http://dev.openwengo.com/mailman/listinfo/wengophone-devel