Inactive memory

[vlad-i-mir]

Hello again!
I am continue qBittorrent testing.
Meantime I noticed one not good thing - when I am downloading something like 10-20 GB (or more) or uploading torrents for 2-3 hours my 'inactive ram' fills up with 10GB or more till 99,9%. Totally I have 16 GB RAM in my Mac Mini. So with this all my RAM will be used, causing things like video playback in vlc to crash, freezes etc.
In order to free the inactive memory I type the 'purge' command in Terminal, but that's far from ideal.
When I tried downloading a large file with Transmission/utorrent there is no problem like this at all.
Apart from this recent issue I like to keep using qBittorrent, so is there something I can do or is this a bug in qBittorrent?
Any help will be much appreciated!

[Peter]

So basically it eats up all your free memory?
Not just file cache?

[vlad-i-mir]

Quite correct. It eats all free memory. Not in the same minute, but during a few hours.
I tried with cache - 64, 128, 256, 512 MB and 0 (auto mode).
Nothing succeed - the same.

[Peter]

So far so good, but I'll keep it running for a few days.

[vlad-i-mir]

Thanks for reporting back.
I began test with you in the same time:

[Peter]

Wow, it eats up 1.45gb private memory?
That is surely a memory leak in libtorrent...
(I'll report back later.)

[vlad-i-mir]

ScreenShot after 50 minutes of process:

[vlad-i-mir]

ScreenShot after 3-4 hours:

[Peter]

It happens here as well. Went up to 600MB+ private usage.
I think this will be a libtorrent bug... but we will have to wait for the new version (with new libtorrent). If that behaves bad as well, time to report the bug at libtorrent's bugtracker.

!This is not a bug in qBittorrent.

[vlad-i-mir]

And the last screenshot...

[Peter]

Okay Vladimir, now we will have to wait for a new version.
You can make a script (schedule it) so it restarts qBittorrent every few hours.
If that's an option for you.

[vlad-i-mir]

Shiki, thank you. I completely understand you.
I made last screenshot only for full history.

By the way, how do you think?
May be we will report about the libtorrent's bug before the new version? Or it is useless?

[Peter]

I don't think we have to report it for now.
The alpha version is already out (qBittorrent), and it will use the new libtorrent.

All we can do is wait, and use the workaround (if you want to.)
http://superuser.com/questions/126907/how-can-i-get-a-script-to-run-every-day-on-mac-os-x

I can look around for a solution if you want to. (To get a script that would restart your client every few hours.)
The script would only do this:
1) kill (gracefully) qbittorrent
2) run qbittorrent

[sledgehammer_999]

I am curious what does the "purge" command actually do? Any links?

This may be a bug/feauture related to the way the OS handles the disk cache. We had a similar problem on Windows ~1 year ago...

[Peter]

It is a bug, 100%.
I've been running my virtual machine and the private memory just growing and growing.
There is no end to it, there is a definite leak.

However, I'll run this overnight with constant screenshotting to see what happens.

Is it hard to compile rasterbar + qBittorrent on OS X? (I hate compiling stuff on Windows, as it's a tedious process.. but maybe it's easier on OS X?)
SO I could try the latest and see if it's got the same bug.