synaptic crashed with signal 7 in _int_malloc()

Bug #1303222 reported by Adolfo Jayme Barrientos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Medium
Unassigned

Bug Description

Not sure about how to reproduce. I may be this machine's low memory, bah.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: synaptic 0.81.1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
CurrentDmesg.txt:
 [ 34.892887] r8169 0000:07:00.0 eth0: link up
 [ 34.892898] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 36.093179] init: plymouth-upstart-bridge main process ended, respawning
 [ 44.404719] init: plymouth-upstart-bridge main process ended, respawning
 [ 132.245018] systemd-timedated[2492]: /etc/localtime should be a symbolic link to a timezone data file in /usr/share/zoneinfo/.
Date: Sat Apr 5 17:44:23 2014
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2014-02-23 (41 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140221)
ProcCmdline: synaptic
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 LANGUAGE=es_MX:es
 SHELL=/bin/bash
Signal: 7
SourcePackage: synaptic
StacktraceTop:
 _int_malloc (av=av@entry=0xb68df420 <main_arena>, bytes=bytes@entry=6) at malloc.c:3389
 __GI___libc_malloc (bytes=6) at malloc.c:2891
 g_malloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_value_set_string () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: synaptic crashed with signal 7 in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Adolfo Jayme Barrientos (fitojb) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=av@entry=0xb68df420 <main_arena>, bytes=bytes@entry=6) at malloc.c:3389
 __GI___libc_malloc (bytes=6) at malloc.c:2891
 g_malloc (n_bytes=n_bytes@entry=6) at /build/buildd/glib2.0-2.40.0/./glib/gmem.c:97
 g_strdup (str=str@entry=0x9d3b9e0 "Hecho") at /build/buildd/glib2.0-2.40.0/./glib/gstrfuncs.c:356
 g_value_set_string (value=value@entry=0xbf833b7c, v_string=0x9d3b9e0 "Hecho") at /build/buildd/glib2.0-2.40.0/./gobject/gvaluetypes.c:1038

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in synaptic (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Since it's an error in malloc, you're probably correct about running out of memory. Try increasing swap partition/file size.

information type: Private → Public
Revision history for this message
Popolon (popolon) wrote :

I had the same problem with an upgrade from 13.04 to 14.04 on a laptop with 4 GB of RAM. I hopefully looked at the output console during the crash alert, and this was related to a font installation, that is already a good clue. Don't know which one, could be a chinese one, as it's used on this system.

After upgrade tool crashed, I tried to restore some coherent state on the system. then I launched synaptic from a term, and mostly everything is frozen with lot of erros about gtk in the term. I can't log anymore from the pure text console (ctrl+alt+f1) and X11 is frozen since at least 10 minutes

Revision history for this message
Popolon (popolon) wrote :

After rebooting, I used a console terminal to log and had the following message :

No tallog stackframe at ../source3/param/loadparm.c:4684, leaking memory

Revision history for this message
Popolon (popolon) wrote :

Managed to finish the install by rebooting and using apt-get to install remaining packages.

The taillog strackframe message occur at each sudo action

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.