lcalc is too verbose (mysterious "Warning: new stack size")

[williamstein]

I tried one simple example "by hand" that actually uses lcalc, and was not pleased by what happened:

sage: E = EllipticCurve('37a')
sage: L = E.lseries()
sage: L.zeros(10)
  ***   Warning: new stack size = 1030944 (0.983 Mbytes).
[0.000000000, 5.00317001, 6.87039122, 8.01433081, 9.93309835, 10.7751382, 11.7573247, 12.9583864, 15.6038579, 16.1920174]
sage: L.zeros(10)
  ***   Warning: new stack size = 1030944 (0.983 Mbytes).
[0.000000000, 5.00317001, 6.87039122, 8.01433081, 9.93309835, 10.7751382, 11.7573247, 12.9583864, 15.6038579, 16.1920174]

Basically, every time you use lcalc to do anything with elliptic curve L-series, you get some mysterious warning (of course, really output from PARI). However, the problem has been in released Sage for a long time. It was in sage-4.7.

Depends on #9640

Component: interfaces

Keywords: lcalc

Author: Jeroen Demeyer

Branch/Commit: u/jdemeyer/ticket/11985 @ f609cb0

Reviewer: Travis Scrimshaw

Issue created by migration from https://trac.sagemath.org/ticket/11985

[jdemeyer]

Dependencies: #9640

[jdemeyer]

Milestone sage-4.7.3 deleted

[jdemeyer]

Branch: u/jdemeyer/ticket/11985

[sagetrac-git]

Commit: d2ae836

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

d2ae836

Use pari_init_stack() instead of old allocatemoremem()

[sagetrac-git]

Changed commit from d2ae836 to f609cb0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

f609cb0

Use pari_init_stack() instead of old allocatemoremem()

[jdemeyer]

Author: Jeroen Demeyer

[fchapoton]

Changed keywords from none to lcalc

[tscrim]

Reviewer: Travis Scrimshaw

[tscrim]

comment:10

Looks good to me.

[vbraun]

comment:12

I got this on mod during a doctests (somewhat random failure):

sage -t --long src/sage/schemes/elliptic_curves/lseries_ell.py
**********************************************************************
File "src/sage/schemes/elliptic_curves/lseries_ell.py", line 243, in sage.schemes.elliptic_curves.lseries_ell.Lseries_ell.zeros
Failed example:
    E.lseries().zeros(2)
Expected:
    [0.000000000, 5.00317001]
Got:
      ***   Warning: not enough memory, new stack 1000000000.
    [0.000000000, 5.00317001]
**********************************************************************
File "src/sage/schemes/elliptic_curves/lseries_ell.py", line 246, in sage.schemes.elliptic_curves.lseries_ell.Lseries_ell.zeros
Failed example:
    a = E.lseries().zeros(20)             # long time
Expected nothing
Got:
      ***   Warning: not enough memory, new stack 1000000000.
**********************************************************************
1 item had failures:

This is also with #13163 but I'm pretty sure this ticket is the culprit...

[jdemeyer]

comment:13

Please confirm that the system you were building this on was not low on memory. From reading the PARI sources, it looks like that message can only occur after a failed malloc(). You should make sure doctests have 2.5GB of memory available.

[vbraun]

comment:15

As I said its on mod, so a pretty beefy machine with 128GB ram. Of course I don't know exactly what happened, but I think its pretty unlikely that some runaway process ate everything except 2% of the available ram such that only this doctest failed. Twice in a row.

[jdemeyer]

comment:16

Don't forget that mod also runs the Sage Notebook server, which might make your scenario more likely. Were you testing many jobs in parallel? And were those the only doctest failures that you got?

[vbraun]

comment:17

That was the only failure in the whole build process and, at least when I checked later, there were tons (~50GB) of free memory. The buildbot always tests the same number of processes, no more, no less.