[Dchub-dev] [Bug #3233] memoryleak somewhere

[nobody]

=================== BUG #3233: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3233&group_id=3963

Changes by: Eric PREVOTEAU <address@hidden>
Date: Thu 04/17/2003 at 16:16 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
             Release | 0.4.1_CVS                 | 0.4.2_CVS


------------------ Additional Follow-up Comments ----------------------------
is your hub registered ? I have already found 3 memory leaks (not yet commited).



=================== BUG #3233: FULL BUG SNAPSHOT ===================


Submitted by: hhgoth                  Project: DcHub:  Hub software for Direct 
Connect
Submitted on: Wed 04/16/2003 at 11:36
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  0.4.2_CVS                   Platform Version:  Linux x86          
Planned Release:  None                Fixed Release:                        

Summary:  memoryleak somewhere

Original Submission:  Memusage of dchub raised up to 90MB on a hub with around 
100Users in a week

Follow-up Comments
*******************

-------------------------------------------------------
Date: Thu 04/17/2003 at 16:16       By: ericprev
is your hub registered ? I have already found 3 memory leaks (not yet commited).

-------------------------------------------------------
Date: Wed 04/16/2003 at 19:30       By: hhgoth
without cluster...
I restarted the hub around 12 - now the memusage is 2 1/2 from start

-------------------------------------------------------
Date: Wed 04/16/2003 at 18:31       By: ericprev
with or without cluster ?


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3233&group_id=3963