FiTADiNE

Results 12 comments of FiTADiNE

> Why do you report about previous versions? Just for additional information. Main report about last version.

@adem4ik, sorry, there was a mistake in libtorrent ver. My current version is 1.2.17.0 already. ![Scr460](https://user-images.githubusercontent.com/31488363/188679995-199fd725-805c-4816-bde6-f1c49eb1f4d1.png)

@adem4ik, probably, in prev releases there was RAM limit, but now it's disk cache limit. Omg... Thanks, i'll try it.

@adem4ik, still the same. @ElectricityMachine, just windows dark theme. ![Scr461](https://user-images.githubusercontent.com/31488363/188810286-ac007496-08f6-42a7-ab1c-b431fa3cedea.png)

@pulbitz, best way is downgrading to 4.3.9?

![qB 4 4 3 1](https://user-images.githubusercontent.com/31488363/188891810-81c484bf-7593-4363-84db-70df06e3fd73.png) Working Set limit 1024MB. ![PE 4 4 3 1](https://user-images.githubusercontent.com/31488363/188891855-2bbf7389-21f7-4e36-9b46-a468b8f780d4.png) 25% of 32GB RAM used after 15 minutes. (Work around application stuttering on Windows not fixed...

@stalkerok, already decided in [1st post](https://github.com/qbittorrent/qBittorrent/issues/17680#issue-1362761450).

@glassez, yes, cuz it's older version on libtorrent 2 with Working set limit parameter and w/o memory leak. [Here](https://github.com/qbittorrent/qBittorrent/issues/17680#issue-1362761450) you can see 2 screenshots: 1066MB qB usage with total 88%...

@stalkerok, no, should i? And why? @glassez, lolwhat? 1st screen: qB works, 88% of 32GB RAM. Second: qB closed, 21% of 32GB RAM. What kind of screenshot do you need?...

> Where it is seen what exactly uses all these memory. Okay, where could i see it? > Since you provide reports about different qBittorrent version don't forget to attach...