On Thu, Mar 18, 2021 at 8:29 PM Volker Braun wrote:
>
> This is presumably the same memory leak as in
> https://trac.sagemath.org/ticket/31340
yes, and it can be fixed by just removing custom memory allocators in ZZ.
>
> On Thursday, March 18, 2021 at 7:21:14 PM UTC+1 m.derick...@gmail.com
This is presumably the same memory leak as in
https://trac.sagemath.org/ticket/31340
On Thursday, March 18, 2021 at 7:21:14 PM UTC+1 m.derick...@gmail.com wrote:
> Hi Vincent,
>
> Thanks for testing and good that you realized that indeed looked fishy
> indeed.
>
> I think your extension of my
Hi Vincent,
Thanks for testing and good that you realized that indeed looked fishy
indeed.
I think your extension of my code with multiple loops actually confirms
that there is a problem even after warming up:
the prints:
memory usage 30k: 1771.8046875
memory usage 40k: 1771.80859375
mean
Sorry, your example indeed looks fishy.
Le 18/03/2021 à 17:36, Vincent Delecroix a écrit :
Maarten, in your example your can not fairly compare the first
and second run. For example R is not allocated at your first
call of "mem = get_memory_usage()". Also Integers have a pool
which is likely
Maarten, in your example your can not fairly compare the first
and second run. For example R is not allocated at your first
call of "mem = get_memory_usage()". Also Integers have a pool
which is likely not being filled at startup. Ignoring the first
run, I do not notice any difference.
(both on
Hi Guys,
Thanks for the replies. I think this is enough info to know that it happens
on multiple systems and that it's not just the cocalc enhanced version of
sage. I have created:
https://trac.sagemath.org/ticket/31511#ticket for this.
In the meantime I found the problem is already with the
On MacBook Air Mid 2012, with Sage 9.2,
39
0
memory usage 10k: 5.0
0
memory usage 20k: 11.0
On Thursday, March 18, 2021 at 10:01:56 AM UTC-5 David Joyner wrote:
> On Thu, Mar 18, 2021 at 6:56 AM Maarten Derickx
> wrote:
>
>> Hi All,
>>
>> tldr: the bottom of this post contains example
On Thu, Mar 18, 2021 at 6:56 AM Maarten Derickx
wrote:
> Hi All,
>
> tldr: the bottom of this post contains example code of which I would like
> the results on some other systems.
>
> I recently encountered a memory leak in the relatively innocently looking
> code:
>
> d = 27
> M = 109
> for i
Hi All,
tldr: the bottom of this post contains example code of which I would like
the results on some other systems.
I recently encountered a memory leak in the relatively innocently looking
code:
d = 27
M = 109
for i in range(1):
for a in srange(M):
for r in srange(d):
