Giant memory leaks still there



 H,

 Kudos for making Beagle work without inotify! Also kudos for fixing
libexif issue. I am able to run Beagle for first time in this year.

 Previously, I never had problems with beagle leaking memory. But now
beagled uses metric tons of RAM:
  PID USER      PR  NI  VIRT  RES  SHR WCHAN     %CPU %MEM   TIME COMMAND     
20788 zdzichu   25  10  358m 292m 4116 322529193  0.0 58.1   0:02 mono-beagled --debug /usr/lib/beagle/BeagleDaemon
20789 zdzichu   26  10  358m 292m 4116 322529193  0.0 58.1   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon
20790 zdzichu   25  10  358m 292m 4116 -          0.0 58.1   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon
20799 zdzichu   25  10  358m 292m 4116 -          0.0 58.1   0:43 mono-beagled --debug /usr/lib/beagle/BeagleDaemon
20800 zdzichu   25  10  358m 292m 4116 -          0.0 58.1   0:18 mono-beagled --debug /usr/lib/beagle/BeagleDaemon

 (argh!)

 Beagle version - CVS about half an hour old.
% mono --version
Mono JIT compiler version 1.1.4, (C) 2002-2004 Novell, Inc and
Contributors. www.go-mono.com
        TLS:           normal
        GC:            Included Boehm (with typed GC)
        SIGSEGV      : normal
        Globalization: none

 Environment: Slackware -current.

 Also, why text size in BEST is two times larger than three months ago?
I'm not vision-impaired, really, previous text size was OK.

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station
zdzichu irc -nie spam- pl    wagon filled with backup tapes." -- Jim Gray




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]