4 ms·

Sorry to hear you're having problems. We need more data to take any kind of action. Are there particular sites that cause problems? Do you have any extensions i

Sorry to hear you're having problems. We need more data to take any kind of action. Are there particular sites that cause problems? Do you have any extensions installed? Even better: can you visit about:memory and use the "Measure and save..." button to get a snapshot of memory usage when it gets high? You can then either email it to me or (preferably) file a bug at bugzilla.mozilla.org and CC me. Bugzilla can be intimidating, but don't worry too much about getting every field right. Just make sure the description is clear. If all that is too hard (hopefully not!), you could try just resetting Firefox: https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems https://support.mozilla.org/en-US/kb/reset-firefox-easily-fi.... That's not a guaranteed fix, but it does help in a lot of cases.

annnnd 12y ago
Thanks for taking your time to answer, will try to provide as much info as possible. I didn't notice any particular pages which would cause problems, but OTOH there must be a pattern to the pages I visit. I am using FireBug, Abduction, Add to search bar, Greasemonkey (disabling now - didn't know I had it enabled), NoScript and Pencil. Since this happens during normal course of work I would rather send memory usage patterns privately if that's OK with you. The challenge will be to catch FF when the machine hasn't started swapping yet (by then I can count myself lucky if I can still issue killall firefox). Will try to send you "measure and save" output as soon as possible. Thanks!
- nnethercote 12y ago
  Greasemonkey scripts often cause bad behaviour, though it of course depends on the particular scripts enabled. Firebug can also slow things down a lot, even if it's not enabled. (Apparently Firebug 2.0 is better in this regard.) Selectively disabling extensions isn't the most fun game in the world, but it's often effective in working out if one is causing problems. And private email for the about:memory data is fine. For my email address, take my HN username and append @mozilla.com.

annnnd 12y ago

Thanks for taking your time to answer, will try to provide as much info as possible. I didn't notice any particular pages which would cause problems, but OTOH there must be a pattern to the pages I visit. I am using FireBug, Abduction, Add to search bar, Greasemonkey (disabling now - didn't know I had it enabled), NoScript and Pencil. Since this happens during normal course of work I would rather send memory usage patterns privately if that's OK with you. The challenge will be to catch FF when the machine hasn't started swapping yet (by then I can count myself lucky if I can still issue killall firefox). Will try to send you "measure and save" output as soon as possible. Thanks!

nnethercote 12y ago
Greasemonkey scripts often cause bad behaviour, though it of course depends on the particular scripts enabled. Firebug can also slow things down a lot, even if it's not enabled. (Apparently Firebug 2.0 is better in this regard.) Selectively disabling extensions isn't the most fun game in the world, but it's often effective in working out if one is causing problems. And private email for the about:memory data is fine. For my email address, take my HN username and append @mozilla.com.