usb-creator-gtk crashed with SIGSEGV in malloc_consolidate()

Bug #868462 reported by Till Kamppeter
50
This bug affects 8 people
Affects Status Importance Assigned to Milestone
eglibc (Ubuntu)
Invalid
High
Unassigned
usb-creator (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Happened on the attempt to get the ISO of Oneiric beta2 onto a 60GB USB hard disk. Shortly after copying the files, when it installed the boot loader it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: usb-creator-gtk 0.2.34
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Oct 5 17:19:36 2011
ExecutablePath: /usr/bin/usb-creator-gtk
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd419ca8d96 <malloc_consolidate+198>: mov 0x8(%rbx),%rdx
 PC (0x7fd419ca8d96) ok
 source "0x8(%rbx)" (0x100000007) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 malloc_consolidate (av=0x7fd419fca1c0) at malloc.c:5153
 malloc_consolidate (av=0x7fd419fca1c0) at malloc.c:5115
 _int_malloc (av=0x7fd419fca1c0, bytes=1024) at malloc.c:4373
 __GI___libc_malloc (bytes=1024) at malloc.c:3660
 ?? ()
Title: usb-creator-gtk crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (4 days ago)
UserGroups:

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
visibility: private → public
Changed in usb-creator (Ubuntu):
importance: Undecided → High
milestone: none → oneiric-updates
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=0x7fd419fca1c0) at malloc.c:5153
 malloc_consolidate (av=0x7fd419fca1c0) at malloc.c:5115
 _int_malloc (av=0x7fd419fca1c0, bytes=1024) at malloc.c:4373
 __GI___libc_malloc (bytes=1024) at malloc.c:3660
 time_strftime (self=<optimized out>, args=<optimized out>) at ../Modules/timemodule.c:504

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in usb-creator (Ubuntu):
importance: High → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in usb-creator (Ubuntu):
status: New → Confirmed
tags: added: quantal running-unity
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

The problem seems to occur in various situations, not only with usb-creator, seems to be somewhere in malloc.

Changed in eglibc (Ubuntu):
importance: Undecided → High
Changed in usb-creator (Ubuntu):
importance: Medium → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in eglibc (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

almost certain this doesn't belong to eglibc. the root cause for this can be in any other component. glibc is just the messanger

Changed in eglibc (Ubuntu):
status: Confirmed → Incomplete
Adam Conrad (adconrad)
Changed in eglibc (Ubuntu):
status: Incomplete → Invalid
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.