gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
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-
ProcVersionSign
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 16 22:41:21 2017
ExecutablePath: /usr/bin/
ProcCmdline: gnome-system-
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f4917a25162 <__GI__
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-
StacktraceTop:
__GI___libc_free (mem=0x55c10000
get_process_
proctable_
update_
create_
Title: gnome-system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users
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.