Re: Beagle on FC3

2005-01-28 Thread Gen Zhang
I'm curious about this memory usage thing -- because I haven't been
affected by it, almost from the point I started playing around with
Beagle, which was back in november-ish. At that point, beagled would
usually die before it ate any significant amount of memory -- and now
I generally keep it running for a day or two without any noticable
increase in hoggishness.

Perhaps it has something to do with the mono versions/distro packaging?

Gen


On Thu, 27 Jan 2005 12:28:30 -0500, Joe Shaw [EMAIL PROTECTED] wrote:
 On Thu, 2005-01-27 at 16:41 +0100, Bart Vanbrabant wrote:
  Hello,
 
  I finally got beagle (0.0.5) working on FC3 without breaking hal by
  using dbus 0.23. I installed mono from the dag.wieers.be This is version
  1.0.5 but there are quite some problems.
 
 There are now packages from the mono guys which may work better.
 
 1.0.5: http://www.go-mono.com/archive/1.0.5/fedora-3-i386/
 1.1.3: http://www.go-mono.com/archive/1.1.3/fedora-3-i386/
 
 For some reason they're not on the web page yet...
 
  Beagle starts fine but after a while it starts using all my memory and
  making the whole computer unuseable. I start beagle with beagled --fg
  --debug. When a crawling thread starts, after about 5 to 15 files the
  memory usage goes from 20% to 100% and my pc starts swaping. This
  happens in about 5 seconds. When I kill beagle the memory usage goes
  to 20%, this means that beagle uses about 400mb ram in less then 5
  seconds time. Is there a way to find out what the problem is?
 
 Does the daemon seem to hang at a certain point?  It sounds like maybe a
 filter is running away with things.  Yeah, beagle is a bit of a mem hog,
 but it's not *that* bad.  The last few lines of the log may be helpful.
 
  There are some other problems. I compiled a custom 2.6.10 with inotify.
  Everytime I reboot I have to chmod 644 /dev/inotify. I already added the
  inotify:root:root:0666 to /etc/udev/permissions.d/50-udev.permissions
  like the ubuntu wiki says but this doesn't work.
 
 Dunno what to tell you about that one.  It looks like it should work.
 
  And the last problem is that mono crashes sometimes with this error
  (before it starts eating my memory) with an error like this
  *** glibc detected *** free(): invalid pointer: 0x09239800 ***
  I also get this error when I open a note in tomboy or want to create a
  new note. This is probably mono related, how can I solve this?
 
 This error is pretty common on 1.0.x at the end of a program, but I'm
 not aware of it crashing a program mid-run.  Try the mono packages
 linked above (particularly 1.1.x) to see if it's more stable.
 
 Joe
 
 ___
 Dashboard-hackers mailing list
 Dashboard-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/dashboard-hackers

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


beagle-0.0.5: Problem crawling a dir containing a .pdf file

2005-01-28 Thread Daniele Bellucci
I'm running beagled-0.0.5.

beagled --fg --debug

[...]
INFO: Crawling /home/belch/Desktop/DoC/ipv6
DEBUG: Finished task File System Crawler in ,00s
DEBUG: Starting task ipv6
DEBUG: Flushing...
DEBUG: - file:///home/belch/Desktop/DoC/ipv6/ipv6tutorial.pdf
DEBUG: + file:///home/belch/Desktop/DoC/ipv6/ipv6tutorial.pdf
DEBUG: Loaded 19 filters from /opt/mono-1.0/lib/beagle/Filters/Filters.dll

** (unknown:5291): WARNING **: : bogus daemon response, type 0

** ERROR **: file handles.c: line 1737 (_wapi_handle_process_fork):
should not be reached
aborting...


The contents of ipv6 directory is:
ls -a /home/belch/Desktop/DoC/ipv6/:

. .. ipv6tutorial.pdf



The above problem doesn't occours when beagle scan other directories
contaning more .pdf files.

Do i need to supply any additional info?




___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


beagle now support both dbus 0.23 and CVS

2005-01-28 Thread Joe Shaw
Hey,

I just checked in some configure check and conditional code so that
beagle should now build and work against both the old dbus API (in 0.23)
and the new dbus API (CVS/0.30).

I'm going to keep the NLD/SUSE snapshots building 0.23 however, since
things like galago haven't been updated yet.

Let me know if you run into any problems.

Joe

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


required inotify kernel upgrade

2005-01-28 Thread Robert Love
Everyone, please read this, if you can read.

As of right now, Beagle-CVS is incompatible with the previous inotify
kernels and patches.

Inotify has moved to a dynamically allocated and sized filename payload.
This means that the average inotify event is significantly smaller, yet
inotify can support filenames of any size.  The introduction of dynamic
sized filenames required a bit of effort, due to alignment issues
requiring null padding, but the patch has been out there for awhile
(inotify 0.18) and I just finished the Beagle work.

SUSE 9.1, 9.2, NLD9, and SLES9 users can use the following Grand Unified
Kernels:

http://primates.ximian.com/~rml/kernel-rml/suse-92-i586/

Roughriders who compile from scratch can use the following patch,
against 2.6.10:

http://www.kernel.org/pub/linux/kernel/people/rml/inotify/v2.6/0.18/inotify-0.18-rml-2.6.10-9.patch

Hopefully the other distros who build kernel packages will update to
0.18 soon.  The patch has been out for awhile now.

This is, we hope, the last (major) ABI/API change to Inotify.

Happy hacking,

Robert Love


___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers