On 9/1/07, mabshoff <[EMAIL PROTECTED]> wrote: > > I think William should decide soon if Bug Day 2 will be moved up a day > to Thursday. it looks very likely to happen, so please let us know and > update the Wiki page.
Nodoby was against it, so SAGE Bug Day 2 will be this coming *Thursday*, from 10am until ... I've updated the wiki. > One more update remark on memleaks: > > William suspected a leak in > "a=ModularSymbols(n,sign=1).decomposition()" related to linear > algebra, specifically the following code > > for n in range(10,100): a=ModularSymbols(n,sign=1).decomposition(); > print n, get_memory_usage() > > leads to > > ==5107== LEAK SUMMARY: > ==5107== definitely lost: 14,051,359 bytes in 1,679,059 blocks. > ==5107== indirectly lost: 470,430 bytes in 12,425 blocks. > ==5107== possibly lost: 396,558 bytes in 1,064 blocks. > ==5107== still reachable: 168,316,769 bytes in 635,979 blocks. > ==5107== suppressed: 0 bytes in 0 blocks. > > Ouuch. > > I have analyzed the log and opened 8 new tickets in trac and tagged > them for 2.8.4. Most seem pretty straight forward. I also retagged the > other memleak tickets (expect the Cython problem I reported earlier > tonight) for 2.8.4, which brings us to 18 open memleak tickets for > 2.8.4. Let's see how we fare until the 2.8.4 release, but I am > optimistic :) > > If you have any code that seems to be leaking memory please keep some > simple examples (preferably running stuff in a loop) and retry with > 2.8.4. If it still leaks just post to sage-devel and I will take a > look as time permits. Yes! SAGE really really needs to be as memory-leak free as possible. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
