cairo-dock crashed with signal 5 in g_realloc()

Bug #1283268 reported by nam1962 on 2014-02-21
This bug affects 8 people
Affects Status Importance Assigned to Milestone
cairo-dock (Ubuntu)

Bug Description

Cairo-dock crashed, happens randomly

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: cairo-dock-core 3.3.99.beta1.1~20140219~bzr1717-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Fri Feb 21 23:01:33 2014
ExecutablePath: /usr/bin/cairo-dock
InstallationDate: Installed on 2013-09-09 (165 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130909)
ProcCmdline: cairo-dock
Signal: 5
SourcePackage: cairo-dock
 g_realloc () from /lib/x86_64-linux-gnu/
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_object_freeze_notify () from /usr/lib/x86_64-linux-gnu/
 gtk_widget_unparent () from /usr/lib/x86_64-linux-gnu/
Title: cairo-dock crashed with signal 5 in g_realloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

nam1962 (amauryat) wrote :

 g_realloc (mem=mem@entry=0x39edf40, n_bytes=103079215112) at /build/buildd/glib2.0-2.39.90/./glib/gmem.c:167
 g_data_set_internal (dataset=0x0, new_destroy_func=<optimized out>, new_data=<optimized out>, key_id=56, datalist=0x2ca1380) at /build/buildd/glib2.0-2.39.90/./glib/gdataset.c:471
 g_datalist_id_set_data_full (datalist=datalist@entry=0x2ca1380, key_id=56, data=data@entry=0x222e110, destroy_func=destroy_func@entry=0x7fb9f718e220 <g_object_notify_queue_free>) at /build/buildd/glib2.0-2.39.90/./glib/gdataset.c:670
 g_object_notify_queue_freeze (object=object@entry=0x2ca1370, conditional=conditional@entry=0) at /build/buildd/glib2.0-2.39.90/./gobject/gobject.c:236
 g_object_freeze_notify (object=0x2ca1370) at /build/buildd/glib2.0-2.39.90/./gobject/gobject.c:1101

Changed in cairo-dock (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matthieu Baerts (matttbe) wrote :

Hello and thank you for this bug report!

I'm not sure that it's due to the dock but is it possible to have more details about this bug? Is it possible to reproduce it every time?
According to the Stacktrace, it seems that you had this bug after having opened/closed a menu, is it correct? Then the dock will crash when freeing memory because GTK/GLib tries to allocate bytes (~100Go of RAM), it's a bit too much :-)

@fabounet: any idea? :-)

information type: Private → Public
nam1962 (amauryat) wrote :

Hi !
A this stage it's really random by me.
I'm on Trusty, so I did'nt mind much ;)
I sometimes launch several programs, then waiting for them to open.
If I get more clues on specifics, i'll leave them here.

The only odd stuf I noticed is that, usually it restarts easilly by relaunching cairo, but I had an instance where, i had a "ghost" instance of cairo behind the operating relaunch untill reboot.

to give you clues on my memory management, I set my /etc/sysctl.conf to :

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cairo-dock (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers