unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Damien Mattei <damien.mattei@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: GC Warning: Repeated allocation of very large block
Date: Mon, 19 Sep 2022 12:04:04 +0200	[thread overview]
Message-ID: <CADEOadfLWSr-4NbwYqEEqxWcoU82RXeoxD3iOmhF2yUSG-ytsg@mail.gmail.com> (raw)

hello,
on an intensive computation of symbolic calculus running since 10 days
approx. on a desktop, i get now this message since yesterday,and  in the
computation of C12 (still waiting):

GC Warning: Repeated allocation of very large block (appr. size 84377600):
May lead to memory leak and poor performance

it is now at : size 121749504, i suppose one of my symbolic expression get
big!
is this message appearing when a single scheme variable reach a given size?

i wanted to debug and trace because i know this algorithm expand a lot
expressions (perheaps too much) sometimes (but it is an NP-problem and
exponential, so perheaps stop the program is the only solution and run it
on more little data)
i do not think there could be a memory leak in a recursive scheme program,
at least not like in C ,i'm not allocating memory and i do not to set-car!
or set-cdr! that perhaps could loose the GC.

Damien

C1 = #t
C1 = T

C2 = T

C3 = (B1 ∨ B2)

C4 = (B2 ∨ (B1 ∧ B3))

C5 = ((B1 ∧ B3) ∨ (B2 ∧ B3) ∨ (B2 ∧ B4) ∨ (B3 ∧ B4))

C6 = ((B1 ∧ B3 ∧ B5) ∨ (B2 ∧ B3 ∧ B5) ∨ (B2 ∧ B4) ∨ (B3 ∧ B4) ∨ (B4 ∧ B5))

C7 = ((B1 ∧ B3 ∧ B5) ∨ (B2 ∧ B3 ∧ B5) ∨ (B2 ∧ B4 ∧ B6) ∨ (B3 ∧ B4 ∧ B6) ∨
(B4 ∧ B5) ∨ (B5 ∧ B6))

C8 = ((B1 ∧ B3 ∧ B5 ∧ B7) ∨ (B2 ∧ B3 ∧ B5 ∧ B7) ∨ (B2 ∧ B4 ∧ B6) ∨ (B3 ∧ B4
∧ B6) ∨ (B4 ∧ B5 ∧ B7) ∨ (B5 ∧ B6) ∨ (B6 ∧ B7))

C9 = ((B1 ∧ B3 ∧ B5 ∧ B7) ∨ (B2 ∧ B3 ∧ B5 ∧ B7) ∨ (B2 ∧ B4 ∧ B6 ∧ B8) ∨ (B3
∧ B4 ∧ B6 ∧ B8) ∨ (B4 ∧ B5 ∧ B7) ∨ (B5 ∧ B6 ∧ B8) ∨ (B6 ∧ B7) ∨ (B7 ∧ B8))

C10 = ((B1 ∧ B3 ∧ B5 ∧ B7 ∧ B9) ∨ (B2 ∧ B3 ∧ B5 ∧ B7 ∧ B9) ∨ (B2 ∧ B4 ∧ B6
∧ B8) ∨ (B3 ∧ B4 ∧ B6 ∧ B8) ∨ (B4 ∧ B5 ∧ B7 ∧ B9) ∨ (B5 ∧ B6 ∧ B8) ∨ (B6 ∧
B7 ∧ B9) ∨ (B7 ∧ B8) ∨ (B8 ∧ B9))

C11 = ((B1 ∧ B3 ∧ B5 ∧ B7 ∧ B9) ∨ (B10 ∧ B2 ∧ B4 ∧ B6 ∧ B8) ∨ (B10 ∧ B3 ∧
B4 ∧ B6 ∧ B8) ∨ (B10 ∧ B5 ∧ B6 ∧ B8) ∨ (B10 ∧ B7 ∧ B8) ∨ (B10 ∧ B9) ∨ (B2 ∧
B3 ∧ B5 ∧ B7 ∧ B9) ∨ (B4 ∧ B5 ∧ B7 ∧ B9) ∨ (B6 ∧ B7 ∧ B9) ∨ (B8 ∧ B9))

GC Warning: Repeated allocation of very large block (appr. size 84377600):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102641664):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102653952):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102678528):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102690816):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102739968):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102764544):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102789120):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102825984):


             reply	other threads:[~2022-09-19 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 10:04 Damien Mattei [this message]
2022-09-19 11:44 ` GC Warning: Repeated allocation of very large block Olivier Dion via General Guile related discussions
2022-09-19 17:26   ` Damien Mattei
2022-09-21  9:42     ` Damien Mattei
2022-09-21  9:48       ` Damien Mattei

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=CADEOadfLWSr-4NbwYqEEqxWcoU82RXeoxD3iOmhF2yUSG-ytsg@mail.gmail.com \
    --to=damien.mattei@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).