Spent some time with this, and found the cause. The error is a bit mis- leading, it's not a double-free-problem. Rather, it's a problem with the implementation failing to allocate space for null-termination when allocating buffer for an empty screen-line, therefore the connection to terminal size.
The allocation is most likely rounded up to even numbers, so for an odd number, the null-character will be allocated anyways (or the glib corruption-sensors only reacts on every odd byte). In any case, here's a patch that solves it. -- aptitude assert failure: *** glibc detected *** aptitude: double free or corruption (!prev): 0x08f9d658 *** https://bugs.launchpad.net/bugs/515525 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
