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

[Tydyn Rain St. Clair]

It seems this is connected to Chrome or an extension.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: indicator-application 12.10.1+14.04.20140407-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CrashCounter: 1
CrashDB: unity
CurrentDesktop: Unity
Date: Tue Feb 3 13:17:57 2015
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationDate: Installed on 2014-05-30 (249 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, no user)
 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
upstart.unity-panel-service-lockscreen.log:
 *** BUG ***
 In pixman_region32_init_rect: Invalid rectangle passed
 Set a breakpoint on '_pixman_log_error' to debug

[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.