Ok, some more recent thoughts on the matter.
My debugging has given me a ballpark idea of whats going on, although
this is by no means definitive, its merely me trying to put a finger
on where beagled/mono is not only playing directly with glibc alot,
but basically where it does this in the file
I removed the CVS version from my system and reinstalled 0.1.1. Beagle has been running for ~4hr now with no glib-related crashes. Note that neither mono nor the various helper app depenencies has changed in any way -- as of yesterday running CVS, beagle would crash in less than an hour with the
It may be a helper app, but it's not just debian. I'm running the latest CVS under gentoo (on AMD64) and have the same issue:Debug: Done crawling '/home/jdaluz/Tori Amos/Tori Amos - photo Gallery'*** glibc detected *** double free or corruption (!prev): 0x01a92bb0 ***
Debug: The daemon
-- Forwarded message --
From: Kevin Kubasik [EMAIL PROTECTED]
Date: Oct 21, 2005 12:59 PM
Subject: Re: Glib malloc exception
To: Jose daLuz [EMAIL PROTECTED]
Just guessing, perhaps its something with the sqlite libs? Beagle
requires sqlite 2.x, while the current release
Gentoo keeps both sqlite 2.x and 3.x available in separate slots, and both are installed on my system. I don't see anything on this error in Gentoo bugzilla re sqlite (or beagle, or other packages that I could find for that matter).
From: Kevin Kubasik
[EMAIL PROTECTED]Just guessing, perhaps its
Well now, after the last crash my indexes are being recreated from scratch. The interesting thing is that the old indexes, all 133MB worth, are still there. This is also after enabling the firefox extension in 1.5b2, but I don't think that's the problem.
-- Jose M. daLuz508-287-2146[EMAIL
oddly enough, after wiping the ./.beagle folder, i was able to index
about half of my home directory before this
Debug: Done crawling '/home/kevin/Documents/TEMPusb'
*** glibc detected *** free(): invalid next size (normal): 0x095d5150 ***
DebugAborted
: The daemon appears to have gone away.
Hi,
On Tue, 2005-10-18 at 08:09 -0400, Kevin Kubasik wrote:
Hey, I recently updated to the latest mono (1.1.9.2) and am still
getting this error, can anyone offer any direction as to the problem?
When run without the File backend, this does not occur, my best guess
is that one of the 'glue'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm running the current CVS of beagle, as the daemon starts up, I
glean the following error.
*** glibc detected *** malloc(): memory corruption: 0x08ec5cf0 ***
(I've included a full log of the startup below)
It always appears after 2 directories have
