From: "qhwang" <qhwang@ieeta.pt>
To: Sandro Dangui <sdangui@nortelnetworks.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: out of memory
Date: Wed, 8 Oct 2003 13:36:16 +0100 [thread overview]
Message-ID: <003e01c38d98$c45ed300$70ab88c1@ieeta.pt> (raw)
In-Reply-To: 31E38B53D182D51195FA00508BE3A33402CE4C9B@zwnbc004.cala.nortel.com
> Do you have recursive calls?
> If you alloc all memory you need in the beginning, then the only problem
> that I can figure is that you have an infinite recursive call... or a loop
> between calls. It may be causing a stack overflow.
In my program there is a loop over 10k iteratives (image). In each loop
there are some kind of statistical learning algorithm running. It is killed
after it uses about 650 MB space (code + mainly data) with my laptop after
out of memory and swap. I believe the problem lies inside the loop but
there should be no infinite loop because when I reduce the loop to over 1k
iteratives the program runs well. In this case it uses more 100 MB space.
I wonder where is this huge data space requirement coming from, since there
is no memory allocation inside the loop?
> BTW: You have problems with your e-mail:
It's very strange.
QingHua
next parent reply other threads:[~2003-10-08 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31E38B53D182D51195FA00508BE3A33402CE4C9B@zwnbc004.cala.nortel.com>
2003-10-08 12:36 ` qhwang [this message]
2003-10-08 15:07 ` out of memory qhwang
2003-10-08 15:22 ` ronkhu
2003-10-08 16:31 ` qhwang
[not found] ` <1065630558.3f843b5e20715@www.correo.unam.mx>
2003-10-08 16:45 ` qhwang
2003-10-09 11:00 ` qhwang
2003-10-08 12:44 Sandro Dangui
2003-10-08 13:31 ` Mariano Moreyra
2003-10-08 13:38 ` Piyush Jain
-- strict thread matches above, loose matches on Subject: below --
2003-10-08 11:34 qhwang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003e01c38d98$c45ed300$70ab88c1@ieeta.pt' \
--to=qhwang@ieeta.pt \
--cc=linux-c-programming@vger.kernel.org \
--cc=sdangui@nortelnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).