Hi Martyn
Am 12.05.2014 um 15:19 schrieb Martyn Russell <mar...@lanedo.com>:
> On 12/05/14 14:11, Ralph Böhme wrote:
>> Hi all,
>
> Hi Ralph,
>
>> I have no idea why the realloc() fails in glib. My first thought was
>> that there may be a memory leek somewhere, but checking this with
>> Solaris libumem didn't come up with any serios leaks:
>>
>> root@beast:~# mdb /opt/csw/libexec/tracker-extract
>> /var/cores/core.tracker-extract.2763 Loading modules: [ libumem.so.1
>> libc.so.1 ld.so.1 ]
>>> ::findleaks
>> CACHE LEAKED BUFCTL CALLER 080c9590 1 080e7350
>> libglib-2.0.so.0.4000.0`g_mutex_impl_new+0x23
>> ------------------------------------------------------------------------
>>
>> Total 1 buffer, 32 bytes
>>>
>>
>> Go figure. :( Ideas?
>
> Does it happen each time you index a particular file or is the file
> itself not important?
these are actuall all the same files. :)
root@beast:~# find /tank/dbd/dir* | wc -l
6344
root@beast:~# find /tank/dbd/dir* | md5sum | sort | uniq
d4f59517bb0e4362f123633408d78239 -
root@beast:~# head /tank/dbd/dir/file1.txt
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
Hamburg
root@beast:~# ls -lh /tank/dbd/dir/file1.txt
-rw-r--r-- 1 ralph staff 1.2M May 12 13:54 /tank
The crash is always happening at a different file.
> I.e. is it an accumulative effect or isolated to one case?
Some sort of accumulative effect.
_______________________________________________
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list
