It's ok. I get that too. It's the TLS data associated with the main=20
thread, and it is intentionally never freed. It's not a leak since it
is a= =20
one-time allocation. I really do not know what is going on in your=20
machine.
After RSS was ~60MB:
* addr=0x080be6b8 size=892
On Wed, 16 Jun 2004, [iso-8859-1] S=F6nke Ruempler wrote:
It's ok. I get that too. It's the TLS data associated with the main=3D2=
0
thread, and it is intentionally never freed. It's not a leak since it
is a=3D =3D20
one-time allocation. I really do not know what is going on in your=3D20
Remember to shut down the server cleanly before reporting the leak
log.
Here the XMail.memleaks file for now:
* addr=0x080be6b8 size=892
from=0x0809863b
from=0x0808e1b5
from=0x08055df1
from=0x08055f03
from=0x0806be27
from=0x0806c15c
from=0x0806c357
On Sat, 5 Jun 2004, [iso-8859-1] S=F6nke Ruempler wrote:
Remember to shut down the server cleanly before reporting the leak
log.=20
=20
Here the XMail.memleaks file for now:
=20
* addr=3D0x080be6b8 size=3D892
from=3D0x0809863b
from=3D0x0808e1b5
from=3D0x08055df1
Sönke Ruempler wrote:
Memchecker runs now on the main server. I'll let it run until RSS is
40MB.
And then upgrade the server :-)
The problem is that if RSS goes over X, the system just kills XMail process,
no matter if you have 40 MB or GB RAM :/
You must have missed earlier messages of
You must have missed earlier messages of Davide then. You should
upgrade your glibc library on that machine.
glibc-2.2.4-13
glibc-common-2.2.4-13
glibc-devel-2.2.4-13
gcc-2.96-98
--
Mit freundlichem Gruß
Sönke Ruempler
Technik
top concepts Internetmarketing GmbH
Am Steinkamp 7 -
On Fri, 4 Jun 2004, [iso-8859-1] S=F6nke Ruempler wrote:
You must have missed earlier messages of Davide then. You should
upgrade your glibc library on that machine.
=20
glibc-2.2.4-13
glibc-common-2.2.4-13
glibc-devel-2.2.4-13
gcc-2.96-98
Remember to shut down the server cleanly
I am looking into making a patch to integrate my leak-tracer in
XMail. It= =20
worked better than valgrind yesterday :-/
That would be great since my XMail installations are still leaking (41MB RSS
now on main server, running since 2004-05-31)
--
Sönke
-
To unsubscribe from this list: send
On Thu, 3 Jun 2004, [iso-8859-1] S=F6nke Ruempler wrote:
I am looking into making a patch to integrate my leak-tracer in
XMail. It=3D =3D20
worked better than valgrind yesterday :-/
=20
That would be great since my XMail installations are still leaking (41MB =
RSS
now on main server,
Sönke Ruempler wrote:
I am looking into making a patch to integrate my leak-tracer in
XMail. It= =20
worked better than valgrind yesterday :-/
That would be great since my XMail installations are still leaking (41MB RSS
now on main server, running since 2004-05-31)
Ran the mem debug
Ran the mem debug version here for several day and no leaks were
detected!
Memchecker runs now on the main server. I'll let it run until RSS is 40MB.
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line
Sönke Ruempler wrote:
Ran the mem debug version here for several day and no leaks were
detected!
Memchecker runs now on the main server. I'll let it run until RSS is 40MB.
And then upgrade the server :-)
--
Groeten,
Peter
This message will self-destruct in 10 seconds...
-
- Heb je een
Memchecker runs now on the main server. I'll let it run until RSS is
40MB.
And then upgrade the server :-)
The problem is that if RSS goes over X, the system just kills XMail process,
no matter if you have 40 MB or GB RAM :/
-
To unsubscribe from this list: send the line unsubscribe xmail in
Davide Libenzi wrote:
1.20 release files are available here:
http://www.xmailserver.org
This fixed the possible memory leak and the use-after-free bug:
http://www.xmailserver.org/ChangeLog.html#may_30__2004_v_1_20
I definitely recommend to update to 1.20
Ok, now running on the
On Mon, 31 May 2004, [iso-8859-1] S=F6nke Ruempler wrote:
Davide Libenzi wrote:
1.20 release files are available here:
=20
http://www.xmailserver.org
=20
This fixed the possible memory leak and the use-after-free bug:
=20
http://www.xmailserver.org/ChangeLog.html#may_30__2004_v_1_20
15 matches
Mail list logo
