Htop reports the thread memory usage multiple times. Basically the
total memory used is 76MB for beagled and 37MB for index-helper, one
once for each.
This is not a bug.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact list
> Debug output attached.
Can you run with --mono-debug and attach that output ? There is a
slight chance beagled might hang after it prints the detail stacktrace
in which case just kill -9 the process afterwards.
This is probably the evolution-sharp crash that jjohnny is working on.
I forgot the
> Yes the socket exist but is dead because of a crashed beagle (forgot the
> evolution# issue?).
>
> [EMAIL PROTECTED]:~$ stat .beagle/socket
> File: `.beagle/socket'
> Size: 0 Blocks: 0 IO Block: 4096 socket
> Device: 806h/2054d Inode: 328351 Links: 1
>
> I can reproduce this bug with the following versions:
>
> [EMAIL PROTECTED]:~$ dpkg -l beagle | grep ii
> ii beagle 0.3.5-1
> indexing and search tool for your personal data
> [EMAIL PROTECTED]:~$ dpkg -l libbeagle1 | grep ii
> ii li
On 4/20/08, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote:
> Processing commands for [EMAIL PROTECTED]:
> > reassign 476610 beagle
> Bug#476610: gnome-color-chooser: Won't start
> Bug reassigned from package `gnome-color-chooser' to `beagle'.
...
> > retitle 476610 beagle: EAGAIN prevents ap
> So here is a debug log which I attach, it shows a crash, maybe its
> useful.
This has been reported by others too. Its a fatal crash in evolution-sharp.
I believe you can disable/uninstall evolution-data-server backend to
avoid the crash.
E.g. reported here
http://bugs.archlinux.org/task/1012
6 matches
Mail list logo
