Re: [sage-devel] Re: memory management issue: deleted variables not released

2017-08-09 Thread Denis Sunko
Hi all, the problem went away when I switched from 32-bit debian jessie to 64-bit stretch. One would suspect a bug in some of the system libraries, because the version of Sage is the same (and compiled locally from source). Obviously the motivation to find it went down somewhat. I thank everyone

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-28 Thread Denis
Bill: your comment about normal/expected behavior covers my initial post, but not the fact that the same code works in 7.0 and crashes in 7.3. So the question is, might someone with developer's tools catch this problem quickly even with my vanilla code - it's just 277 lines total, plus the

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-28 Thread 'Bill Hart' via sage-devel
You don't need to post all your code, just a small example that demonstrates the problem you are experiencing. If your computation is using half the memory on the machine, the solution is likely going to be to find a way to make it use less memory or to get a machine with more memory. The

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-28 Thread Denis
Jonathan, thank you for this thoughtful analysis. With a really simple function, I get the output 0 1066.03125 0 1066.03125 0 1066.1640625 0 1066.1640625 0 1066.29296875 0 1066.29296875 0 1066.29296875 0 1066.29296875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-27 Thread Jonathan Bober
I just noticed this thread because of your recent reply, and happened to read through. (I haven't regularly read sage-devel for a while.) As to your original email: I think there is a subtle python memory management issue there. If you run sage: BIG=myfunction(somevars) sage:

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-27 Thread Denis
Tried but it didn't work out. MathCloud admins say they can't help. Tried also at SageCell but the calculation wouldn't end either way after several hours. Any ideas? Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Re: memory management issue: deleted variables not released

2016-09-21 Thread William Stein
On Wed, Sep 21, 2016 at 10:46 AM, Denis wrote: > > I tried to reproduce the issue in the cloud, but it cannot do it with the > default settings. Although I can check that my code works, the benchmark > calculation cannot complete because of the limitations of the free

[sage-devel] Re: memory management issue: deleted variables not released

2016-09-21 Thread Denis
I tried to reproduce the issue in the cloud, but it cannot do it with the default settings. Although I can check that my code works, the benchmark calculation cannot complete because of the limitations of the free account. To make a realistic comparison I need 4G of RAM and unlimited timeout

[sage-devel] Re: memory management issue: deleted variables not released

2016-09-11 Thread Denis
Thanks for the idea to post the example on the cloud. I will try to do that, but can't begin before Sept. 20. Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email

[sage-devel] Re: memory management issue: deleted variables not released

2016-09-10 Thread Dima Pasechnik
On Saturday, September 10, 2016 at 6:56:04 AM UTC, Denis wrote: > > > As far as I am concerned, development of Sage stopped at 7.0 - I tried 7.3 > yesterday, and could not do a mid-level benchmark calculation, which I have > been repeating since at least 6.4. The problem is a memory fault. 7.0

[sage-devel] Re: memory management issue: deleted variables not released

2016-09-10 Thread Samuel Lelievre
Sat 2016-09-10 08:56:04 UTC+2, Denis on sage-devel: > As far as I am concerned, development of Sage stopped at 7.0 - I tried > 7.3 yesterday, and could not do a mid-level benchmark calculation, which > I have been repeating since at least 6.4. The problem is a memory fault. > 7.0 is the last

[sage-devel] Re: memory management issue: deleted variables not released

2016-09-10 Thread Denis
As far as I am concerned, development of Sage stopped at 7.0 - I tried 7.3 yesterday, and could not do a mid-level benchmark calculation, which I have been repeating since at least 6.4. The problem is a memory fault. 7.0 is the last version with which I can do it. I am prepared to collaborate

[sage-devel] Re: memory management issue: deleted variables not released

2016-05-12 Thread Denis
Sorry for the stupid question - I did not realize that some old sources are to be found among the new sources :) Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an

[sage-devel] Re: memory management issue: deleted variables not released

2016-05-12 Thread Denis
Thanks for the suggestions, I will try to do that. In the meantime, I tried 7.1 on a machine with 100G of RAM. Now it works, but it costs me 4.3 G of RAM the first time round - that is the same calculation which used 1G in 7.0. Re-running it a few times with or without clobbering BIG - I am

[sage-devel] Re: memory management issue: deleted variables not released

2016-05-11 Thread Nils Bruin
On Wednesday, May 11, 2016 at 8:15:50 AM UTC-7, Denis wrote: > > I wonder if the developers think this is a bug. From the user's point of > view it is certainly strange that one cannot invoke the same function call > twice in a row. > > Memory leaks are usually bugs, although in some cases, the

[sage-devel] Re: memory management issue: deleted variables not released

2016-05-11 Thread Dima Pasechnik
On Wednesday, May 11, 2016 at 4:30:37 PM UTC+1, Denis wrote: > > > Sorry, forgot to mention: all this is happening under Sage 7.0. Under 7.1 > it is much worse, I get a silent "Memory exhausted" crash the FIRST time > round, without a report. So it seems something really broke between 7.0 and

[sage-devel] Re: memory management issue: deleted variables not released

2016-05-11 Thread Denis
Sorry, forgot to mention: all this is happening under Sage 7.0. Under 7.1 it is much worse, I get a silent "Memory exhausted" crash the FIRST time round, without a report. So it seems something really broke between 7.0 and 7.1. -- You received this message because you are subscribed to the