On Tue, 2005-12-20 at 17:59 +0100, Michael Haubenwallner wrote: > Hi, > > My problem is that my ORBit2-Server's memory consumption is growing, > which leads to a real problem if running for some days. > > Attached is a file containing the backtraces for the problematic > allocations causing the memory grow, as they are allocated for each new > connection, but are not freed when this connection is closed.
I think this got fixed in CVS HEAD. Try the latest CVS and see if that fixes it for you. -- jules > These are not real memory 'leaks' in valgrind/purify speaking, as they > are stored in some list, which is freed at shutdown, but in fact they > never get reused in my environment, so, for me, they _are_ leaks. > > When digging into the code, i found this comment: > > linc2/src/linc-connection.c at link_connection_state_changed_T_R(): > > case LINK_DISCONNECTED: > ... > /* don't free pending queue - we could get re-connected */ > ... > > What if this reconnect never occurs ? > > Is it possible somehow to get this 'pending queue' freed without server > shutdown ? > Or - which requirements must a client meet to get reconnected ? > > Thanks > haubi > > _______________________________________________ > orbit-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/orbit-list _______________________________________________ orbit-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/orbit-list
