[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-gnunet] ARGH! error message
From: |
Christian Grothoff |
Subject: |
Re: [Help-gnunet] ARGH! error message |
Date: |
Wed, 15 Oct 2003 19:06:04 -0500 |
User-agent: |
KMail/1.4.3 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 15 October 2003 03:36 am, Hendrik Pagenhardt wrote:
> Tonight GNUnet died (after running for about one and a half day):
>
> Oct 15 03:01:23 ARGH!
> Oct 15 03:01:23 __BREAK__ at logging.c:220
>
> Which means some component tried to allocate more than 40 MB of memory.
> I don't see why this is fatal, but nevertheless it occurred. Under which
> circumstances can this happen? Is there a configuration option I can
> tune, which will prevent it? My system has 512 MB of memory and gnunetd
> typically allocates about 35-50 MB of it.
Hmm. That's more than what it allocates for me (gnunetd on ovmj.org takes more
like 12 MB), but it is probably just that you are sharing more data (the
quota has an effect on memory use by the database module). About the 40 MB
allocation, well, yes, that's bad. I didn't intend to keep the check in the
code (it was there to debug an unrelated problem), but now that we know that
there can be a problem...
I've modified the code in CVS to make it print *where* the problematic
allocation occured. Just "cvs up" and please report if you can reproduce it
(I believe that it should be a bug to allocate one chunk of 40 MB, that could
be fatal for quite a few machines :-).
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/jeDs9tNtMeXQLkIRAuuTAJ0V/0763GzNSb9wsyP2ze1NhxTw1ACfXob8
YeNiUI7iq9C7EALcualyHvw=
=mfKX
-----END PGP SIGNATURE-----