ABP eats too much memory

[konstbel]

Hello
I have found, that ABP eats too much memory. Usually it needs ~65Mb, but sometimes grab up to 700Mb!!!
Why so much???
(sorry, don't understand how to attach image of Chrome Task Manager here, to show the memory consumption)

[mapx]

- you can upload an image on imgur.com and then post here the link
- what filter lists are enabled in ABP ?
-

sometimes grab up to 700Mb

well does this mean only for some heavy or broken pages ? examples ?

[gpspilot]

I have found, that ABP eats too much memory. Usually it needs ~65Mb, but sometimes grab up to 700Mb!!!
Why so much???

700 MB would indeed be bad. But I often see ABP use twice as much as that: 1.45 GB! A lot more than the Chrome browser itself, and a lot more than the OS X kernel_task process. In this screenshot, ABP is Process ID 405, and processes are sorted by memory usage in Activity Monitor as well as Chrome Task Manager:



My Macbook Pro has only 8 GB, and this amount of memory usage is definitely slowing it down -- pushing the OS X "Memory Pressure" into the red. Is there a really bad memory leak?

ABP 3.3.2
Chrome 69.0.3497.100
Max OS X 10.10.3 (I have my reasons for not upgrading)
only 10 whitelisted domains, no custom filter list

Now that the "Bug reports" forum is closed, I'm not clear on how to file a Bug Report. Does this post constitute a bug report?

[mapx]

You could post your issue and all the details on the bug tracker
https://issues.adblockplus.org

However, if you already tested your issue in a new / clean profile, you could further test another adblocker (just to see the difference)

ublock origin:
https://chrome.google.com/webstore/deta ... iagm?hl=en

(while testing uBo keep ABP disabled)

[gpspilot]

You could post your issue and all the details on the bug tracker
https://issues.adblockplus.org

Hmm, looks like the registration I just created doesn't work there and I'll need to create a second registration.

This inefficiency is caused by the fact that at en/bugs, it says to report bugs in the forum, not the bug tracker. So that in itself is a bug that should be reported.