gnome-system-monitor crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #958958 reported by Montag
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gnome System Monitor
Fix Released
Critical
gnome-system-monitor (Ubuntu)
Fix Released
Medium
Robert Roth

Bug Description

Using 12.04 Beta, upgraded from 11.10.

I accessed the 'properties' of a process (whoopsie if it's relevant) and tried to scroll over those properties. Not sure if it was that, but the System Monitor then closed. This bug has been created automatically by the system, I'm just adding what I was doing in the hope is useful...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
Uname: Linux 3.2.0-19-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 18 23:11:50 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: gnome-system-monitor
SegvAnalysis:
 Segfault happened at: 0xb63eda14 <vfprintf+12836>: repnz scas %es:(%edi),%al
 PC (0xb63eda14) ok
 source "%es:(%edi)" (0x67726faa) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-system-monitor
StacktraceTop:
 vfprintf () from /lib/i386-linux-gnu/libc.so.6
 __vasprintf_chk () from /lib/i386-linux-gnu/libc.so.6
 g_vasprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdup_printf () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-system-monitor crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to precise on 2012-03-18 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Montag (adancs) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=0xbfa04770, format=<optimized out>, ap=0xbfa048b8 "") at vfprintf.c:1621
 __GI___vasprintf_chk (result_ptr=0xbfa0487c, flags=1, format=0x8081210 "%s (%d)", args=0xbfa048b4 "/org") at vasprintf_chk.c:68
 vasprintf (__ap=0xbfa048b4 "/org", __fmt=0x8081210 "%s (%d)", __ptr=0xbfa0487c) at /usr/include/i386-linux-gnu/bits/stdio2.h:199
 g_vasprintf (string=0xbfa0487c, format=0x8081210 "%s (%d)", args=0xbfa048b4 "/org") at /build/buildd/glib2.0-2.31.20/./glib/gprintf.c:314
 g_strdup_vprintf (format=0x8081210 "%s (%d)", args=0xbfa048b4 "/org") at /build/buildd/glib2.0-2.31.20/./glib/gstrfuncs.c:509

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 gnome-system-monitor (Ubuntu):
importance: Undecided → Medium
summary: - gnome-system-monitor crashed with SIGSEGV in vfprintf()
+ gnome-system-monitor crashed with SIGSEGV in _IO_vfprintf_internal()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-system-monitor (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=683671

Changed in gnome-system-monitor (Ubuntu):
assignee: nobody → Robert Roth (evfool)
status: Confirmed → Fix Committed
Changed in gnome-system-monitor:
importance: Unknown → Critical
status: Unknown → Fix Released
Martin Pitt (pitti)
information type: Private → Public
Revision history for this message
Martin Pitt (pitti) wrote :

Not sure why Launchpad didn't close this automatically.

gnome-system-monitor (3.7.90-0ubuntu1) raring; urgency=low

  [ Robert Roth ]
  * New upstream release (LP: #1130956)
    - Fixed various memory leaks
    - Policykit support to kill/renice other users' processes (LP: #983127)
    - Do not report active programs as sleeping (LP: #174164)
    - Fixed crash in process properties caused by old workaround (LP: #958958)
    - Do not use deprecated API, use new color selection dialogs (LP: #972472)
  * debian/control.in, debian/control
    - bumped gtk-mm and gtk+ to meet the new requirements

 -- Robert Roth <email address hidden> Thu, 21 Feb 2013 12:03:41 +0100

Changed in gnome-system-monitor (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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