On 2016-10-18 12:13, Jeroen Demeyer wrote:
I think it crashes for a different reason: there are some unchecked
allocations in realloc(). This has nothing to do with overcommit.
Fixed at https://trac.sagemath.org/ticket/21720
--
You received this message because you are subscribed to the
I think it crashes for a different reason: there are some unchecked
allocations in realloc(). This has nothing to do with overcommit.
--
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
On 2016-10-17 17:40, Jori Mäntysalo wrote:
Is it even theoretically possible to handle something like Graph(10^10)?
That will crash at the line
memset(self.vertices, NULL, nverts * self.hash_length *
sizeof(SparseGraphBTNode *))
Are you *sure* that it crashes at the above line? It seems to
On Tue, 18 Oct 2016, Jeroen Demeyer wrote:
Setting (as root) the value of /proc/sys/vm/overcommit_memory will not
help
Are you sure? With vm.overcommit_memory set to "2", the error should happen
during allocation.
Yes, I tested that too. Just add print-function before and after the line
I
On 2016-10-17 17:40, Jori Mäntysalo wrote:
Setting (as root)
the value of /proc/sys/vm/overcommit_memory will not help
Are you sure? With vm.overcommit_memory set to "2", the error should
happen during allocation.
--
You received this message because you are subscribed to the Google Groups
On 2016-10-17 17:40, Jori Mäntysalo wrote:
but due to overcommit there is no exception raised.
That's really the fault of the OS, not the fault of Sage.
Side comment: don't use
x = malloc(n)
memset(x, 0, n)
There is calloc for that.
And *certainly* don't use NULL, use 0 for that.
--
You
Is it even theoretically possible to handle something like Graph(10^10)?
That will crash at the line
memset(self.vertices, NULL, nverts * self.hash_length *
sizeof(SparseGraphBTNode *))
Before that we have
sig_malloc(nverts * self.hash_length * . . .
if not . . .
raise
