[haiku-bugs] Re: [Haiku] #13108: [Deskbar] One week running high memory usage

  • From: "mmlr" <trac@xxxxxxxxxxxx>
  • Date: Thu, 15 Dec 2016 00:05:40 -0000

#13108: [Deskbar] One week running high memory usage
------------------------------------+----------------------------
   Reporter:  joy                   |      Owner:  axeld
       Type:  bug                   |     Status:  new
   Priority:  normal                |  Milestone:  Unscheduled
  Component:  Applications/Deskbar  |    Version:  R1/Development
 Resolution:                        |   Keywords:
 Blocked By:                        |   Blocking:  13107
Has a Patch:  0                     |   Platform:  x86
------------------------------------+----------------------------

Comment (by mmlr):

 Replying to [comment:3 pulkomandy]:

libroot_debug does not track leaks, ...

 Yes it does. See the leak_analyser.sh script help for how to invoke an
 executable with leak dumping:

 {{{
 LD_PRELOAD=libroot_debug.so MALLOC_DEBUG=ges50 program > file
 }}}

 The 'e' switch of the MALLOC_DEBUG env enables allocation dumping on exit,
 while 'g' enables the guarded heap (needed to have the info collected) and
 's' enabling/lengthening the allocation vs. deallocation stacktrace.

 Run it through the script to to filter out common false positives and get
 some stats. Either of these outputs can be attached here.

--
Ticket URL: <https://dev.haiku-os.org/ticket/13108#comment:4>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.

Other related posts:

  1. Home
  2. haiku-bugs
  3. Archive
  4. 12-2016