Re: [Tracker] Memory allocation failures during extraction in 0.14.2

[Jürg Billeter <j bitron ch>]

Hi Ken,

On Mon, 2012-08-13 at 12:47 -0400, Ken Schmedding wrote:
> I was getting these failures (as reported in tracker-extract.log in
> verbosity debug) on large files during extraction:
>
> GLib:gmem.c:239 failed to allocate xxx bytes
>
> I did some analysis and found that tracker-extract.log reports:
>        Setting memory limitations: total is 18.4 EB
>        Virtual/Heap set to 268.4 MB
>
> I was confused by this as my Mac Pro running Fedora 16 has 12 GB of
> memory.  Also I was confused by the EB reported for memory as I never heard
> of E bytes

EB stands for Exabyte. 18.4 EB are roughly 2^64 Bytes. From reading the
code it looks like this can happen if /proc/meminfo cannot be parsed for
some reason. In that case we fall back to the minimum limit of 256 MiB
(268.4 MB).

Can you please paste or attach the contents of /proc/meminfo?

I don't like limiting virtual memory in general. We should revisit
whether we (still) need this code at all.

Regards,
JÃrg