unity-panel-service crashed with SIGABRT in g_assertion_message()

[technologiclee]

I was using FireFox and Chrome and used all the ram.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-application 12.10.1+14.04.20140407-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Aug 28 02:52:33 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-annan-standard-precise-amd64-20130106-0
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationDate: Installed on 2014-05-03 (116 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130106-02:29
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, no username)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-application
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gdk_pixbuf_animation_new_from_file () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 gtk_image_set_from_file () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libindicator3.so.7
Title: unity-panel-service crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to trusty on 2014-06-05 (83 days ago)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1332759, 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.