<pvanhoof> (im also proxying the public conversation to them)
<pvanhoof> this is the story: their memory-guys have been giving priority. they saw persistent 10mb of memory usage by tracker-extract
<pvanhoof> i tried, endlessly, to explain them that this is by-design
<juergbi> well, if they talk about 10 MB RSS, optimization can make sense
<pvanhoof> so anyway, i can probably reduce it a little bit by doing g_module_close at some point
<juergbi> what exactly is by design? I don't really remember the tracker-extract details
<pvanhoof> well tracker-extract before was not a long-running process
<pvanhoof> Since carlos' passive-extraction it is
<pvanhoof> They do have a point there
<juergbi> ah, that part
<pvanhoof> btw that it's still 0.17.6 is because of me more than them: I want to move them only after they are really satisfied with the current solution. it was the introduction of the passive-extraction stuff
<juergbi> ok
<pvanhoof> And this issue came out (meaning: they do test memory usage a lot, they saw a increment of memory usage. not a bad thing that they see this)
<pvanhoof> (they are not idiots)
<juergbi> yes, that's a good thing
<pvanhoof> you didn't "opt in" according to them, so you should have gotten 1.0.1
<pvanhoof> or 1.1.4
<juergbi> correct. it's my phone I use daily, I can't risk more issues
<pvanhoof> I pointed out the release you are running and jolla people were amazed you didn't "opt in" :)
<juergbi> it's not like i have a second device for testing
<juergbi> and there are still some bugs in stable releases, so I won't move to beta releases as I expect there to be more issues
<pvanhoof> i tested this and it's ~ correct what they say. it's also the same on desktop
<pvanhoof> precisely why im behind on upstream's releases for jolla :)
<pvanhoof> i know how martyn makes releases :D
<pvanhoof> don't tell martyn :)
<pvanhoof> s/how/when
<juergbi> so I think you should really check in detail what memory is used by the extractor process
<juergbi> part of those 10 MB might not be actual extra RAM usage by tracker-extractor
<juergbi> especially as the heap is only 1.6 MB here
<juergbi> if it's only ~2 MB of system memory usage tracker-extractor is guilty of, you either need to accept this or dissect the heap with memory analysis tools
<pvanhoof> can i share some of this discussion with them?
<juergbi> i doubt dlclose would help much unless we have a library that is bad with regards to global memory usage
<juergbi> and it doesn't look like such a library is in use here based on a quick look at smaps
<juergbi> sure, feel free