cairo-dock crashed with SIGABRT in mem_error()

Bug #1501504 reported by obelix1502 on 2015-09-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cairo-dock (Ubuntu)

Bug Description

When I wanted to shut down the computer with cairo-dock, I received this error.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: cairo-dock-core 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 30 22:45:38 2015
ExecutablePath: /usr/bin/cairo-dock
InstallationDate: Installed on 2015-07-31 (61 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: cairo-dock
 PATH=(custom, no user)
Signal: 6
SourcePackage: cairo-dock
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 __nptl_deallocate_tsd () at pthread_create.c:176
 __nptl_deallocate_tsd () at pthread_create.c:327
Title: cairo-dock crashed with SIGABRT in __nptl_deallocate_tsd()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

obelix1502 (lewillonbruno780) wrote :

 mem_error (format=format@entry=0x7f81066d0ebd "assertion failed: %s") at /build/glib2.0-3UmwzF/glib2.0-2.46.0/./glib/gslice.c:1439
 slab_allocator_free_chunk (chunk_size=chunk_size@entry=112, mem=<optimized out>) at /build/glib2.0-3UmwzF/glib2.0-2.46.0/./glib/gslice.c:1321
 private_thread_memory_cleanup (data=0x7f80b00008e0) at /build/glib2.0-3UmwzF/glib2.0-2.46.0/./glib/gslice.c:785
 __nptl_deallocate_tsd () at pthread_create.c:176
 __nptl_deallocate_tsd () at pthread_create.c:327

Changed in cairo-dock (Ubuntu):
importance: Undecided → Medium
summary: - cairo-dock crashed with SIGABRT in __nptl_deallocate_tsd()
+ cairo-dock crashed with SIGABRT in mem_error()
tags: removed: need-amd64-retrace
Matthieu Baerts (matttbe) wrote :

Hello and thank you for this bug report!

Are you able to reproduce it each time when you want to shut down the computer with Cairo-Dock?
Maybe the dock can no longer allocate new memory when triggering the action to shut down your computer.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers