what is strange is how the Boehm garbage collector can have noticed that
this repeated allocation of memory was a bug?, as it could have be
intentional and normal
Damien
On Wed, Sep 21, 2022 at 11:42 AM Damien Mattei
wrote:
> i think the warning is not a false true because the program at
i think the warning is not a false true because the program at reached in
10 days almost 3Gb :
PID UTIL. PR NIVIRTRESSHR S %CPU %MEMTEMPS+ COM.
332467 mattei20 0 3262260 2,8g 3744 R 215,0 18,4 32277:54
guile
stopping it has released 3 Gb of memory, the
thank you, i think my algorithm is right but can be improved, i have to
work on it,activate tracing to see where is the big expression list and if
it is possible to correct that. There is a main loop in code and the
warning only appear when data is bigger so i do not think of any memory
leak (only
On Mon, 19 Sep 2022, Damien Mattei wrote:
> is this message appearing when a single scheme variable reach a given
> size?
This message is from the bdwgc and not from Guile itself. From their
documentation:
--8<---cut here---start->8---
The garbage collector
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
