[pkmishra]

I have tried it many times but failed. The reason - if firfox memory goes too high, which happens frequently, there is no option to kill single tab(in the stable version) like Google Chrome. I have started using Firefox Nightly (because of separate process feature) but it keeps on crashing. So I am ready to jump on it as soon as we have new stable build with separate process for each tab.

[rockdoe]

1) What do you do to make "Firefox memory goes too high" 2) What does about:crashes say for the crashes you get? Are those known bugs?

[kenrick95]

If you use AdBlockPlus, you can switch to uBlock (https://github.com/gorhill/uBlock) to achieve better memory performance.

[Max_Mustermann]

How painless is the transition with a fairly large collection of custom filters and the like?

[wtallis]

If you use custom filters instead of subscribing to one of the popular filtersets, then you should check to see whether you're even using the kind of rules that ABP doesn't handle well. The memory and CPU usage only gets bad when you've got a lot of broad-spectrum CSS element hiding rules; regular URL-based blocking rules are plenty scalable.

[azdle]

I don't have any custom filters, but AFAIK it uses exactly the same format for its black lists. The "my filters" pages says:

> A filter can be a plain hostname, or an Adblock Plus-compatible filter. Lines prefixed with ‘!’ will be ignored.

[realusername]

For people complaining about the memory usage and using adblock, uBlock really solves everything, it's really night and day.

[lqdc13]

I had the same issue. For me it was pages' JS having bugs or pages recreating ads after adblock blocks them.