From: Catonano <catonano@gmail.com>
To: guile-user@gnu.org
Subject: stack overflow
Date: Sat, 5 Nov 2016 19:33:33 +0100 [thread overview]
Message-ID: <CAJ98PDy-KdM3pBNJ7+PUYqh5A6Tx5MiPB59J0h=f7z3z8Pyjig@mail.gmail.com> (raw)
This procedure of mine
http://paste.lisp.org/display/330424
stack overflows
It run for a very long time and it wrote a 4.9 Mb file, but then it
overflowed
As you can see in "dependencies" I am fetching data from a graph db made
with the Culturia machinery
( https://github.com/amirouche/Culturia/
and
http://hyperdev.fr/notes/a-graph-based-movie-recommender-engine-using-guile-scheme.html
)
I had populated it beforehand, of course.
I was watching it in top while it was ruunning and it took about 30% of the
available memory
Is there anything I can do to make it run until it processes all the input ?
Thanks for any hint
next reply other threads:[~2016-11-05 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 18:33 Catonano [this message]
2016-11-05 18:44 ` stack overflow Amirouche Boubekki
2016-11-05 18:52 ` Catonano
2016-11-05 18:54 ` Catonano
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ98PDy-KdM3pBNJ7+PUYqh5A6Tx5MiPB59J0h=f7z3z8Pyjig@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).