Hi,
> Hi Christoph,
>
> On 10 September 2016 at 23:46, Christoph Cullmann wrote:
Would it be a good idea to restrict the file extractor process to some
>>> fixed amount of memory
to use via setrlimit? (or more fancy stuff?)
>>>
>>> That would probably just make Baloo crash, so fixing t
Hi Christoph,
On 10 September 2016 at 23:46, Christoph Cullmann wrote:
>>> Would it be a good idea to restrict the file extractor process to some
>> fixed amount of memory
>>> to use via setrlimit? (or more fancy stuff?)
>>
>> That would probably just make Baloo crash, so fixing the bug is probab
Hi,
>> If you can consistently repro this, running under valgrind to check for
>> leaks will also go a long way.
>
> https://github.com/taglib/taglib/blob/master/tests/data/toc_many_children.mp3
=> Just as a warning:
if you download that raw and have baloo indexing on, you are pwn'd ;=)
Turn
Hi,
> Hi,
>
> On 10 Sep 2016 19:42, "Christoph Cullmann" wrote:
>>
>> Hi,
>>
>> during the last night of the akademy for me in Berlin, baloo file
> extractor OOM'd my notebook
>> during extracting the tag info of the taglib unit test test-files.
>
> Is it possible to reproduce the issue and get
Hi,
On 10 Sep 2016 19:42, "Christoph Cullmann" wrote:
>
> Hi,
>
> during the last night of the akademy for me in Berlin, baloo file
extractor OOM'd my notebook
> during extracting the tag info of the taglib unit test test-files.
Is it possible to reproduce the issue and get a stack trace?
If yo
Hi,
during the last night of the akademy for me in Berlin, baloo file extractor
OOM'd my notebook
during extracting the tag info of the taglib unit test test-files.
Would it be a good idea to restrict the file extractor process to some fixed
amount of memory
to use via setrlimit? (or more fancy
