unity-2d-panel crashed with SIGSEGV in malloc_consolidate()

[apurv]

Gave this crash after I logged in and started a few programs - Gnome terminal, Firefox, Thunderbird & Empathy.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Sep 22 17:58:20 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: unity-2d-panel
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x739df1d <malloc_consolidate+269>: cmp 0xc(%eax),%esi
 PC (0x0739df1d) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 malloc_consolidate (av=0x74a8400) at malloc.c:5161
 malloc_consolidate (av=0x74a8400) at malloc.c:5089
 _int_free (av=0x74a8400, p=0x9b17af0) at malloc.c:5034
 __GI___libc_free (mem=0x9b17af8) at malloc.c:3738
 QImageData::~QImageData() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
Title: unity-2d-panel crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gwibber-service:2104): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.
 (thunderbird-bin:1972): libebook-WARNING **: e_book_client_new: Cannot get book from factory: Invalid source

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #855752, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.