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

Bug #1665469 reported by dino99
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
Undecided
Unassigned

Bug Description

Got that crash, by:
- right-clicking the mem icon in the systray
- hitting "system monitor ..."

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-system-monitor 3.23.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 16 22:41:21 2017
ExecutablePath: /usr/bin/gnome-system-monitor
ProcCmdline: gnome-system-monitor
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4917a25162 <__GI___libc_free+34>: mov -0x8(%rdi),%rax
 PC (0x7f4917a25162) ok
 source "-0x8(%rdi)" (0x55c0fffffff8) 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=0x55c100000000) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users

Revision history for this message
dino99 (9d9) wrote :
information type: Private → Public
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.

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.