2005/9/19, Joe Shaw <[EMAIL PROTECTED]>:
The zombie processes are a bug in mono. If you upgrade to mono 1.1.8.3or 1.1.9 these should go away. (I also think we worked around a lot ofthem in 0.1.0 but I might be wrong about that.)
Ok, I hope this will be fixed in Ubuntu Breezy soon...
That won't
>What I suggest doing is starting with just the files backend and then
> just the mail backend and see if you see the kind of memory spike you
> have been seeing. If it's in one and not the other (or in both or
> neither) then that helps narrow down the problem.
>
> Thanks,
> Joe
Well, I did as
On Mon, 2005-09-19 at 18:02 -0400, Joe Shaw wrote:
> Hi,
>
> On Mon, 2005-09-19 at 17:55 -0400, Gregory Pierce wrote:
> > I am not sure what to look for. I just typed "beagled --debug-memory
> > --allow-backend" and before this I deleted the .beagle directory. Will
> > this restart the indexing
Hi,
On Mon, 2005-09-19 at 17:55 -0400, Gregory Pierce wrote:
> I am not sure what to look for. I just typed "beagled --debug-memory
> --allow-backend" and before this I deleted the .beagle directory. Will
> this restart the indexing process again? And how can I tell whether the
> problem is in F
On Mon, 2005-09-19 at 17:38 -0400, Joe Shaw wrote:
> Ok. Can you narrow down the backend which is causing the most memory to
> be used, by using the --allow-backend option? Files and Mail are the
> most likely culprits.
Joe,
I am not sure what to look for. I just typed "beagled --debug-memory
Hi,
On Mon, 2005-09-19 at 22:14 +0100, Darren Davison wrote:
> Hi guys, congrats on the 0.1.0 release!
Thanks!
> Now, I'm not yet running a 2.6.13 kernel, so have the wrong inotify version,
> but I'm not sure that's at fault here. My understanding is that inotify won't
> affect the indexer much
Hi guys, congrats on the 0.1.0 release!
I upgraded beagle from 0.0.12 to 0.1.0 and all the various dependencies (I
think I got them all at any rate) and blew away ~/.beagle before starting the
new version just in case.
Now, I'm not yet running a 2.6.13 kernel, so have the wrong inotify version,
Hi,
On Mon, 2005-09-19 at 15:33 -0400, Gregory Pierce wrote:
> Beagle has been working great. I am very pleased with it overall;
> however, I am concerned about its memory usage. The gnome system monitor
> indicates that it is up to 1.1 GB of memory and that swap space (~1GB)
> is at 100% usage.
Check out the discussion (currently going on) at
http://mail.gnome.org/archives/dashboard-hackers/2005-September/msg00069.html
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Hello all,
Beagle has been working great. I am very pleased with it overall;
however, I am concerned about its memory usage. The gnome system monitor
indicates that it is up to 1.1 GB of memory and that swap space (~1GB)
is at 100% usage. Is this normal? I do have a great many files but can
I exp
Joe Shaw ha scritto:
Hi,
** (/usr/lib/mono/1.0/mcs.exe:21547): WARNING **: The following assembly
referen
ced from /usr/lib/mono/gecko-sharp-2.0/gecko-sharp.dll could not be loaded:
Assembly: gtk-sharp(assemblyref_index=2)
Version:2.0.0.0
Public Key: 35e10195dab3c99f
Hi,
On Mon, 2005-09-19 at 13:00 -0400, Joe Shaw wrote:
> Can you run beagled with the --debug-memory flag and then file a bug
> with the logs from ~/.beagle/Log attached? That might give us an idea
> of what is causing the memory usage to get out of hand.
Also, like D Bera suggested, can you nar
Hi,
On Mon, 2005-09-19 at 15:50 +0200, Nico Kaiser wrote:
> @devs:
> Could this be because of shutdown issues? Whenever I shutdown beagle
> (via beagle-shutdown) *or* whenever beagle tries to shutdown one of
> its helpers (when they consume too much memory), I get Zombie
> processes. Beagle stays
Hi,
On Mon, 2005-09-19 at 13:10 +0200, Gregor Hlawacek wrote:
> Found a second (third) issue with beagle 0.1 after running beagled for a
> while (2 hours or so) it uses 800M of memory?
>
> how come
Because there's a bug. :)
> here is the line copied from top:
>
> 16390 seppl 15 0 797m
Hi,
On Sun, 2005-09-18 at 12:25 +0200, Andreas Wasserman wrote:
> Q: I have a large archive of movie trailers, where Beagle could be very
> handy in handing me results quickly, but I rarely use beagle for this
> since it seems to produce weird results depending on what I search for.
>
> Q: Some se
Hi,
> ** (/usr/lib/mono/1.0/mcs.exe:21547): WARNING **: The following assembly
> referen
> ced from /usr/lib/mono/gecko-sharp-2.0/gecko-sharp.dll could not be loaded:
> Assembly: gtk-sharp(assemblyref_index=2)
> Version:2.0.0.0
> Public Key: 35e10195dab3c99f
> The assembl
Hi,
On Sat, 2005-09-17 at 12:59 +0200, Tomasz Torcz wrote:
> Current Beagle from CVS won't start:
>
> (beagled:2164): libebook-WARNING **: Can't find installed BookFactories
>
> Unhandled Exception: GLib.GException: e_book_load_uri: no factories available
> for uri `file:///home/zdzichu/.evolut
Nico Kaiser wrote:
@devs:
Could this be because of shutdown issues? Whenever I shutdown beagle (via
beagle-shutdown) *or* whenever beagle tries to shutdown one of its helpers
(when they consume too much memory), I get Zombie processes. Beagle stays
intact, but the number of its zombie children
It might be useful to know if this is due to any specific backend (
the output of beagle-index-info while beagled is running reports
active backends).
> > Found a second (third) issue with beagle 0.1 after running beagled for a
> > while (2 hours or so) it uses 800M of memory?
> @devs:
> Could t
Hi!
2005/9/19, Gregor Hlawacek <[EMAIL PROTECTED]>:
Found a second (third) issue with beagle 0.1 after running beagled for awhile (2 hours or so) it uses 800M of memory?
@devs:
Could this be because of shutdown issues? Whenever I shutdown beagle
(via beagle-shutdown) *or* whenever beagle tries to
On Mon, 2005-09-19 at 16:38 +0530, Vishy wrote:
> With what version of gtk-sharp2 have you compiled evolution-sharp?
>
> If you have updated gtk-sharp2 recently, you have to recompile
> evolution-sharp with the new version of gtk-sharp2.
>
> Vishy
I am using gtk-sharp 2.5.91 I recompiled both gt
Hi!
Found a second (third) issue with beagle 0.1 after running beagled for a
while (2 hours or so) it uses 800M of memory?
how come
here is the line copied from top:
16390 seppl 15 0 797m 274m 3000 S 32.7 54.5 19:08.08
mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --fg
--deny-b
Hi!
I updated from 0.0.12 to 0.1. Looks nice but still some troubles. I have
troubles with the IMLog backend. When I use it beagle throws some error
messages and doesn't to anything.
Here is the output if I use only the IMLog Backend:
INFO: Starting Gaim log backend
DEBUG: Caught ResponseMessage
23 matches
Mail list logo
