Stefan Lidman <[EMAIL PROTECTED]> wrote: > readline S1, P1
The implementation of readline looks rather bogus. It allocates a huge (64K) string, sets that to zero, and the calls read, which calls readline. This is really suboptimal. It should probably call PIO_buf_readline or such directly, which could return a newly created string of the needed size. WRT the PANIC: interpreter->memory_allocated = 412528944, I don't know yet, why. Printing statistics after the readline makes the PANIC go away but still: Successful *** Parrot VM: Dumping GC info *** Total memory allocated = 384226672 DOD runs = 547 Collect runs = 11 leo
