screen crashes in F17 alpha/beta

[Michal Jaegermann]

On Thu, Apr 19, 2012 at 07:55:56PM -0400, Brian Johnson wrote:
> So, I just got home and tried it on my home machine, three different times.
> This is what I got:
> 
> free(95b724d) bad block. (memtop = 0x96e9800 membot = 0x95ae000)

Use strace and find out what spills those messages.  Looks like a
debugging output but I have no idea from where.

At least addresses apparently passed to free() appear to be in
(membot,memtop) interval but they all are odd numbers which end
in "24d" and that does not look right.  For what it is worth
"4d" is an ascii for "M".

   Michal