On May 3, 12:28 am, [email protected] wrote:
Hi,
Is there any reason you opened a new ticket and did not use #5949 as
mentioned above?
> PS:
>
> > One can then do
> > sage: for p in primes(2,1000000):
> > ....: R.<x,y,z> = GF(p)[]
> > sage: get_memory_usage()
> > 778.35546875
>
> And:
> sage: len(sage.rings.polynomial.polynomial_ring_constructor._cache)
> 34
>
> Hence, indeed, some rings were garbage collected.
I am not sure this fixes the problem mentioned above, but I am still
testing. It might reduce the memory used already, but I won't know for
a while.
> Cheers,
> Simon
As is this patch breaks badly:
sage -t -long devel/sage/sage/rings/number_field/
number_field.py # Segfault
sage -t -long devel/sage/sage/rings/tests.py # Segfault
sage -t -long devel/sage/sage/rings/number_field/
number_field_rel.py # Segfault
sage -t -long devel/sage/sage/rings/number_field/
number_field_element.pyx # Segfault
sage -t -long devel/sage/sage/rings/residue_field.pyx #
Segfault
sage -t -long devel/sage/sage/rings/number_field/
number_field_ideal_rel.py # Segfault
sage -t -long devel/sage/sage/rings/number_field/morphism.py #
Segfault
sage -t -long devel/sage/sage/rings/polynomial/
polynomial_singular_interface.py # Segfault
sage -t -long devel/sage/sage/rings/number_field/unit_group.py
# Segfault
sage -t -long devel/sage/sage/rings/number_field/
small_primes_of_degree_one.py # Segfault
sage -t -long devel/sage/doc/en/bordeaux_2008/nf_orders.rst #
Segfault
sage -t -long devel/sage/sage/rings/number_field/maps.py #
Segfault
sage -t -long devel/sage/sage/schemes/generic/affine_space.py
# Segfault
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
