Welcome,
be aware, that some leaks are *-specific, due to different
pthread-relative mechanisms in Linux and BSD implementations. You can
checkup that pthread_t (and other types from pthread library) in Linux are
int, in BSD they are pointers to kernel-allocated structures. Many of them
created in * code, but some of them never will be destroyed. That's why *
leaks memory, and you can't find leak by astmm. Maybe valgrind can help...
I'll try.
Best regards,
Konstantin Prokazoff
Center Of Excellence, S_V_R Ltd., Kyiv HQs, Ukraine
Official business-partner & DevConnect member of Avaya Inc.
Regional development & support center of Digium Inc.
Tel. +38 044 594 1781, ext. 1038
Fax. +38 044 234 0455
----- Original Message -----
From: "Richard" <[EMAIL PROTECTED]>
To: "Asterisk on BSD discussion" <[email protected]>
Sent: Monday, March 06, 2006 5:12 PM
Subject: [Asterisk-bsd] Thanks for the input . Let me know asap
Thanks for the input on the driver issue. It is what is keeping us from
going
live full asterisk/freebsd right now. The fact it is using up so much
memory.
we also have to attack the mysql mem leak also.when using mysql and
realtime...
With a gig of ram in each server in a 2 week period it gets down to 2.5
meg's
avaible. We then have to restart asterisk on all our boxes. unless there
is a
tool someone knows of to regain mem from a mem leak...
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.1.2/274 - Release Date: 03.03.2006
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
