Hi, I've discovered something kind of interesting - in Sage 5.0, 5.1.beta0, and 5.1.beta1, there seems to be a memory leak somewhere in docstring lookup. Try opening sage in a terminal and top in another terminal. I see the following results:
Open Sage --> RES = 102 MB Type "str?" --> RES = 178 MB Type "str?" --> RES = 234 MB Type "str?" --> RES = 290 MB Type "str?" --> RES = 346 MB Type "str?" --> RES = 402 MB Type "str?" --> RES = 458 MB Type "str?" --> RES = 514 MB ... etc. Each successive lookup causes another 56 MB of memory to be allocated, which as far as I can tell is never freed. Does anyone else see this? Any idea what version of Sage this was introduced in? Note that str() is not even in the Sage library, it's a Python builtin. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
