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

Bug #1665398 reported by Jeremy Bícha
This bug report is a duplicate of:  Bug #1665209: gnome-system-monitor crash on 17.04. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
New
Medium
Unassigned

Bug Description

gnome-system-monitor crashes when I try to view the Processes tab.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-system-monitor 3.23.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 16 11:27:26 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationDate: Installed on 2016-08-11 (188 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
ProcCmdline: gnome-system-monitor -p
SegvAnalysis:
 Segfault happened at: 0x7f035405a162 <__GI___libc_free+34>: mov -0x8(%rdi),%rax
 PC (0x7f035405a162) ok
 source "-0x8(%rdi)" (0x55c4fffffff8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-system-monitor
StacktraceTop:
 __GI___libc_free (mem=0x55c500000000) at malloc.c:2963
 get_process_cgroup_info(ProcInfo&) ()
 proctable_update(GsmApplication*) ()
 update_page_activities(GsmApplication*) ()
 create_main_window(GsmApplication*) ()
Title: gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: Upgraded to zesty on 2016-12-20 (57 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo vboxusers

Revision history for this message
Jeremy Bícha (jbicha) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1665209, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.