Ticket #3760 (new defect)

Opened 5 months ago

Last modified 3 weeks ago

sage -t -long ell_finite_field.py fails with an out of memory error on 32-bit intel os x.

Reported by: was Assigned to: was
Priority: blocker Milestone: sage-3.4
Component: number theory Keywords:
Cc:

Description 

Trying:
    for p in prime_range(Integer(10000)):           #long time (~20s)###line 1014:_sage_    >>> for p in prime_range(10000):           #long time (~20s)
          if p != Integer(389):
              G=E.change_ring(GF(p)).abelian_group()
Expecting nothing

error: no more memory
System 5116k:5116k Appl 4666k/449k Malloc 4088k/3k Valloc 1024k/445k Pages 159/97 Regions 2:2

halt 14  

         [19.0 s]
exit code: 768

----------------------------------------------------------------------
The following tests failed:


        sage -t -long --verbose devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py
Total time for all tests: 19.0 seconds
bsd:sage-3.1.alpha0 was$

Change History

09/04/2008 09:27:49 AM changed by cremona

Could someone with 32-bit intel os x try this again, since it is possible that the patch for #3961 (merged in 3.1.2.alpha2) fixes this.

If not I can try to look into it but I'm not sure how to as it works fine on my laptop.

09/24/2008 01:30:00 AM changed by mabshoff

#4179 is a duplicate of this ticket and has some additional info.

Cheers,

Michael

11/15/2008 02:02:43 PM changed by GeorgSWeber

Just for the record: I had tried to get a grip on this issue, the outcome is trac ticket #4181 --- once that ticket is fixed, this one will (most probably) be resolved, too. Hopefully.

Cheers,
gsw

12/16/2008 07:34:00 PM changed by mabshoff

The following code specifically seems to expose the problem: 

E = EllipticCurve('389a')
for p in prime_range(Integer(10000)): 
    if p != Integer(389):
        G=E.change_ring(GF(p)).abelian_group()

On sage.math the memory increase is about 70 MB with Sage 3.2.2.rc0, so I have no idea how this could fail on OSX.

Cheers,

Michael