Hi again,
On 2019-02-12, Simon King wrote:
> If I recall correctly, valgrind would be able to report leaking memory.
> But how to use it in Sage?
>
> I guess `sage -i valgrind` is the first step. But then? `make start`?
> `sage -ba`? Can you also point me to a valgrind tutorial that
> demonstrate
Hi Justin,
Am Dienstag, 12. Februar 2019 21:45:44 UTC+1 schrieb Justin C. Walker:
>
> I can’t answer most of your questions, but for the last, internet search
> is your friend…
>
>
Of course I did search before asking. However, I believe that
recommendations of people who have actually read a m
Hi, Simon,
> On Feb 12, 2019, at 12:24 , Simon King wrote:
>
> Hi!
>
> Working at #27261, it seems to me that there is a memory leak somewhere
> either in Sage's use of libsingular, or in libsingular internally.
>
> If I recall correctly, valgrind would be able to report leaking memory.
> But
Hi!
Working at #27261, it seems to me that there is a memory leak somewhere
either in Sage's use of libsingular, or in libsingular internally.
If I recall correctly, valgrind would be able to report leaking memory.
But how to use it in Sage?
I guess `sage -i valgrind` is the first step. But then
Hi Dima,
On 2019-02-12, Dima Pasechnik wrote:
> it fixes the leak in the 1st example, but not in the 2nd, according to my
> test.
First I thought so, too. But it seems that the leak has only been
/partially/ fixed.
sage: R. = ZZ[]
sage: import gc
sage: P = (X+Y)^120*Y^100
sage: mem0 = get_memo
Dear Nadim,
On 2019-02-12, Nadim Rustom wrote:
> Just to clarify, I didn't mean to ask whether #13447 itself is causing the
> problem, I was just wondering if these problems were known and whether
> #13447 was meant to fix the memory leak and speed problem. Thanks for your
> efforts.
No probl
Dear Simon,
Thank you for your reply. Indeed I copied the example twice... The second
one just has "Q = P(X+Y,Y)" instead of "Q = P(X,Y)". Or even "Q = P(X+Y,
X-Y)" results in a larger leak.
Just to clarify, I didn't mean to ask whether #13447 itself is causing the
problem, I was just wonderin
On Tue, Feb 12, 2019 at 1:58 PM Simon King wrote:
>
> Hi Nadim,
>
> On 2019-02-12, Nadim Rustom wrote:
> > The following shows a small memory leak:
> > R. = ZZ[]
> >
> >
> > P = (X+Y)^120*Y^100
> >
> >
> > mem1 = get_memory_usage()
> > for i in range(100):
> > Q = P(X,Y)
> > mem2 = get_memory
Hi Nadim,
On 2019-02-12, Nadim Rustom wrote:
> The following shows a small memory leak:
> R. = ZZ[]
>
>
> P = (X+Y)^120*Y^100
>
>
> mem1 = get_memory_usage()
> for i in range(100):
> Q = P(X,Y)
> mem2 = get_memory_usage()
>
>
> print mem2 - mem1
>
>
> whereas the following gives a much bigger
Sorry, I copied the same example twice. The second one (with large leak)
should be
R. = ZZ[]
P = (X+Y)^120*Y^100
mem1 = get_memory_usage()
for i in range(100):
Q = P(X+Y,Y)
mem2 = get_memory_usage()
print mem2 - mem1
tirsdag den 12. februar 2019 kl. 16.28.57 UTC+3 skrev Nadim Rustom:
Hi,
I have recently encountered some issues using multivariate polynomials in
Sage. The most serious is a memory leak, which occurs in the following
examples:
The following shows a small memory leak:
R. = ZZ[]
P = (X+Y)^120*Y^100
mem1 = get_memory_usage()
for i in range(100):
Q = P(X,Y)
The symptoms you described come from the scenario where your gfortran does
not pass initial tests, and so an attempt to build gfortran from source is
made by Sage.
In the output of ./configure there is a list of packages with an indication
which ones are installed, and which ones are used from the
PS: I also disapprove any automatic internet connection without
>> my explicit consent. But I feel like this is secondary here.
>
>
> Sage defaults should work without internet. You should be able to build
> Sage without internet. Etc. For instance, all doctests requiring internet
> are th
> PS: I also disapprove any automatic internet connection without
> my explicit consent. But I feel like this is secondary here.
Sage defaults should work without internet. You should be able to build
Sage without internet. Etc. For instance, all doctests requiring internet
are thus mark
I have installed gcc 8 and gfortran-8 and I have specified gfortran-8 to
the configure file.
The problem is still there.
--
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 ema
It's normal, gcc/g++ and in particular clang/ckang++ are getting
stricter about enforcing standards and bad coding practices. Palp has
not been touched for 7+ years, no wonder...
It would be good to clean these warnings up by fixing the code.
On Tue, Feb 12, 2019 at 1:10 AM Randall wrote:
>
> Is
You are using gcc 4.8.5, which is almost 5 years old (5 years is an
eternity in the world of C/C++/Fortran compilers). Already an older
version of OpenSuse comes with an option of installing gcc 5, see
https://en.opensuse.org/Portal:42.1
Could you try updating your gcc/gfortran?
On Tue, Feb 12, 2
Why neither nbviewer nor binder are able to find
(or serve or ?) these javascript files?
The problem is these lines in src/sage/repl/rich_output/backend_ipython.py
These paths should be changed to take into account the base URL of the
server (don't ask me *how* to do this precisely).
--
Y
18 matches
Mail list logo