*** This bug is a duplicate of bug 1665209 ***
    https://bugs.launchpad.net/bugs/1665209

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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821214/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821216/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821218/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821219/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821220/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821221/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1665828/+attachment/4821222/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1665209
   gnome-system-monitor crash on 17.04

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1665828

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

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Opened System Monitor to check high for CPU usage then close and got
  this crash.

  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
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 17 21:04:36 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2017-02-13 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feee00b2162 <__GI___libc_free+34>:  mov    
-0x8(%rdi),%rax
   PC (0x7feee00b2162) ok
   source "-0x8(%rdi)" (0x5610fffffff8) 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=0x561100000000) at malloc.c:2963
   get_process_cgroup_info(ProcInfo&) ()
   proctable_update(GsmApplication*) ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1665828/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to