3 ms·
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?
by rockdoe 12y ago
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?
- lqdc13 12y agoI had the same issue. For me it was pages' JS having bugs or pages recreating ads after adblock blocks them.
- kenrick95 12y agoIf you use AdBlockPlus, you can switch to uBlock (https://github.com/gorhill/uBlock https://github.com/gorhill/uBlock) to achieve better memory performance.
- Max_Mustermann 12y agoHow painless is the transition with a fairly large collection of custom filters and the like?
- azdle 12y agoI 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.
- wtallis 12y agoIf 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.
- realusername 12y agoFor people complaining about the memory usage and using adblock, uBlock really solves everything, it's really night and day.