Re: re:Re: [Amsn-devel] memleaks update

[Youness A. <kak...@ka...>]

http://amsn.sourceforge.net/forums/viewtopic.php?t=896
would be interesting to limit that event log combo to the last 100 entries  
for example, I'm sure noone will go look more than 100 entries (although,  
I do check for maybe more than 1000 when I need to find something, but in  
that case, I'll just 'tail -n 1000 events.log')
I think that might be the source of my own memleak, I mena, I keep amsn  
open for 2 or more weeks... and I log everything in there (status change,  
etc...) can you imagine how much it could grow ?

p.s.: how about the plugins's array for filtering and -elide idea ?

KKRT

On Wed, 26 Apr 2006 03:51:14 -0400, Karel Demeyer <kmd...@vu...>  
wrote:

>> On Tuesday 25 April 2006 14:14, Karel Demeyer wrote:
>>> Another thread about memleaks ...
>>> I could tackle down some never erased http-'objects' (arrays) but I
>>> think there could be more ... in autoupdate / webcam ?  I'll try to  
>>> find
>>> these too in the future if I'm capable.
>>>
>>>
>>> * the 'objects' arrays msncam.tcl  I didn't take a close look at this
>>> yet but it surely is an issue.  It's not one of my first priorities as  
>>> I
>>> don't know the code and it's only a problem when the webcam gets used  
>>> ..
>>> for just having amsn in your systray it's no problem.
>>>
>>> * why is all the information about the plugins stored in
>>> the ::plugins::plugins array when it's only adressed outside  
>>> plugins.tcl
>>> for autoupdate .. and I think it only needs a tiny bit of this
>>> information ?
>>>
>> It is also used by the GUI selector and some plugins use it to get  
>> information
>> about themselfs (I believe the games plugins uses it to get it's  
>> version). I
>> do agree that it could get a problem if you have lots of plugins  
>> installed as
>> every would have an entry, even if not loaded. As only a limited amount  
>> of
>> information is used by the GUI (author, name, version) and plugin won't  
>> use
>> it unless it's loaded, it would be better to only automaticly load  
>> specific
>> information for a plugin. And later when it gets loaded, load all the  
>> other
>> information (deinit/init procs, namespace) into plugins::plugins.
>
> For the gui: isn't this array recreated every ti;e you open the plugins  
> dialog ?  So it shows new plugins ? ifso, it could flush most of the  
> information when the dialog is closed.  We should have a clear list of  
> what information should be kept in memory and then only keep this;
> * all plugin names and version numbers (for if we would have a  
> dependencies system) -> also not loaded  thus
> * what more ? the autoupdate info ?  then we should keep it and have the  
> auto-updater flush it after usage ?  isnt it only used once ? or more ?
> * ... ?
>
> Karel
>
>>
>>> * I should be sleeping now, ... really !
>>
>> --
>> Karol Krizka
>>
>>
>
> Karel Demeyer
> ICQ-nr.: 167501053  Jabber-ID: mes...@ja...
> MSN-Messenger-ID: mes...@ho...  e-mail: es...@li...
> Homepage: http://student.vub.ac.be/~kmdemeye
>
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job  
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Amsn-devel mailing list
> Ams...@li...
> https://lists.sourceforge.net/lists/listinfo/amsn-devel



-- 
KaKaRoTo