On 8/20/07, Travis E. Oliphant <[EMAIL PROTECTED]> wrote: > > > Memory leaked when allocated from: > > array_buffer_getbuf (arraymodule.c:1775) > > buffer_getbuf (bufferobject.c:28) > > bytes_init (bytesobject.c:807) > > type_call (typeobject.c:429) > > Hmm. I'm not sure what memory is being leaked unless there are > reference counting issues I'm not seeing. > > In bytes_init for example, that line number is a static memory > allocation? How is static memory being leaked?
I'm not sure if this was before or after my checkin, so the line numbers could have been off a bit. > The arraymodule.c malloc call should be gone now as the possible strings > needed are now in the source code itself. That was the only leak AFAIK. So hopefully by removing it there aren't any more. Once there are tests it will be worthwhile to check again. I don't think I checked for refleaks. n _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
