Opened 11 years ago

Last modified 11 years ago

#41542 assigned defect

gnome-system-monitor @3.8.2.1_0 - application crashes when the Resources tab is selected

Reported by: dtsaliki@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: cooljeanius (Eric Gallager)
Port: gnome-system-monitor

Description

  • run gnome-system-monitor
Admins-MacBook-Pro:~ Admin$ gnome-system-monitor
  • click on the "Resources' tab and the application crashes with:
libgtop-server(87978,0x7fff77e97310) malloc: *** error for object 0x7fff56aee9c8: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
glibtop: read 2160 bytes: Resource temporarily unavailable
  • OS version
Admins-MacBook-Pro:~ Admin$ uname -a
Darwin Admins-MacBook-Pro.local 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64
  • XQuartz 2.7.5
  • Xcode version 5.0.2
  • gnome-system-monitor @3.8.2.1_0
Admins-MacBook-Pro:~ Admin$ port installed gnome-system-monitor 
The following ports are currently installed:
  gnome-system-monitor @3.8.2.1_0 (active)
  • libgtop @2.28.5_0
Admins-MacBook-Pro:~ Admin$ port installed libgtop
The following ports are currently installed:
  libgtop @2.28.5_0 (active)
  • Port Version: 2.2.1
Admins-MacBook-Pro:~ Admin$ port version
Version: 2.2.1

Change History (3)

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to devans@…
Port: gnome-system-monitor added

comment:2 Changed 11 years ago by dbevans (David B. Evans)

Status: newassigned

Thanks for this detailed report and my apology for not replying sooner.

After squinting at the screen a lot and several pots of coffee last night, I was able to gain some further understanding of this problem.

  • the problem can be reproduced with the current stable version 3.10.2 and unstable version 3.11.92 (3.12 rc).
  • the actual failure is occurring in libgtop's ${prefix}/bin/libgtop_server2 which is running in a separate process.
  • location of the failure is in the darwin specific implementation of glibtop_get_netload_p()
  • before returning to caller glibtop_get_netload_p() frees a buffer that is passed in as an argument to the function -- this is the failure point.
  • working back through the code now to see how this function gets called and how the buffer in question is allocated.

Hopefully will get to the bottom of this soon.

comment:3 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

Note: See TracTickets for help on using tickets.