New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault on computations in AA, exactify() #18818
Comments
comment:1
Probably |
comment:4
It might be subtle to detect these kinds of things. If you are adding a lot of numbers that belong to a common number field you would better use this number field. Possibly using the ready made function
The ticket #19955 should definitely handle it. However in such case, with #20074 and a little extra help it already "works"
But this current "solution" makes the summation much much slower since some checks are made to see whether the addition could remain in a given number field. |
This comment has been minimized.
This comment has been minimized.
comment:5
Replying to @videlec:
Yes, this is what I'm already using in my application.
Great to hear that work is underway to improve QQbar. |
Basic arithmetic with AA can lead to enormous expression trees, which
easily leads to recursion depth errors and excessive memory use.
(I mentioned this to some developers during the Sage Days in Davis in 2013, but didn't follow up on it.)
might be related to #16222. See also the task ticket #18333.
CC: @vbraun @gagern @videlec
Component: number fields
Issue created by migration from https://trac.sagemath.org/ticket/18818
The text was updated successfully, but these errors were encountered: