NS leaks memory like a firehose on specific site

[amloessb]

When I visit the site http://girlsonfilm.rubberslug.com/ (not categorically NSFW--it's a gallery of old anime cels) NS leaks memory like crazy (~100 MB/s) and very quickly crashes Firefox. I have made this determination because disabling NS causes this to not happen.

Screenshot of about:memory while Firefox was dying: http://puu.sh/3q5Z0.jpg
My NS settings: http://pastebin.com/e4DK3aZb (personal whitelist stripped out, problem unchanged)

As of yet, I have not been able to reproduce the issue using a clean profile and installing NS, even when importing my NS settings from my main profile. I would like advice/assistance in determining what part of my configuration, in conjunction with NS, is causing this issue.

Thank you.

Technical things:
NS version: 2.6.6.6
Windows: 7, 32-bit

[Giorgio Maone]

As of yet, I have not been able to reproduce the issue using a clean profile and installing NS, even when importing my NS settings from my main profile. I would like advice/assistance in determining what part of my configuration, in conjunction with NS, is causing this issue.

This suggests another extension (or user script, if you're using Greasemonkey or Scriptish) is causing the issue when NoScript is present.
Please try Standard Diagnostic to isolate the other factor.

[therube]

Is simply opening that web page (& allowing a couple domains) sufficient to start your memory growth? Or do you need to open multiple pages, various sites, & over time you ramp up?

It is not unexpected for (32-bit) Mozilla to crash (on a x86 OS) once it has used ~1.5 GB of RAM.

Do you get crash reports (about:crashes)? Have you submitted them?
And the report numbers (URLs)?


> I have not been able to reproduce the issue using a clean profile and installing NS

> even when importing my NS settings from my main profile

Are you running the same extensions in each Profile?
(What extensions?)
The same plugins?
(What plugins?)


How about if you fully copy your old profile to a new profile. Using the new, does the problem persist with that copy?

If it does, try disabling other extensions (other then NoScript), one at a time, restarting between, to see if you can find one that cause the issue to go away.

If nothing there, then might try deleting items from your Profile, one at a time, restarting between, again to see if something turns up that way. Start with prefs.js (user.js too, if you're using that). Then perhaps places.sqlite. Then go from there.

---

Just to note...

"that leaked resource doesn't have memory reporters.
Must be a blocker for Bug 563700 - (DarkMatter)."

[amloessb]

I am not at the machine in question, but I will reply to as many questions as I can at this time.

Yes, I only need to open that page, not even allow any domains. This will happen even if it is the first page I open in a session. Once I open the page, there's no stopping the leak; even closing the tab doesn't help. The memory leak is huge, at a rate of ~100 MB/s: I can literally watch Firefox's memory usage tick up by about 100 MB every time the Task Manager refreshes.

I have submitted several crash reports. I'll track them down once I get back home.

I do use Greasemonkey, but the issue still persists with it disabled. That was one of my first suspects.

My plan at this point is to copy over my profile to a new one, confirm that the issue still happens, then perform all testing on that copy. I'll first disable everything except NS, then if the problem has disappeared, perform a binary search on the remaining extensions to determine the one interacting with NS to cause the leak. If i find that NS, by itself, is sufficient to cause the leak, I will try the steps under Profile issues that Giorgio posted.

Thanks for the advice thus far, and I will keep you posted on my progress.

[amloessb]

Some crash reports (ordered newest to oldest):
https://crash-stats.mozilla.com/report/ ... 9ae2130628
https://crash-stats.mozilla.com/report/ ... 0ec2130626
https://crash-stats.mozilla.com/report/ ... 48d2130626
https://crash-stats.mozilla.com/report/ ... 32b2130626

[amloessb]

I have narrowed this down to a combination of NS and FoxyProxy Standard 4.2.

After researching a bit, it seems that the FP team pulled the 4.2 version, but it was not hard-blocked by Mozilla, so while I auto-updated to 4.2 initially, I was never forced to roll back. Installing FP Standard 4.1.4 (current latest version on AMO) fixes this problem.

If anyone wants to try it, you can reproduce by installing NS and Foxy Proxy Standard 4.2 into a clean profile, then visiting the site in question. No special configuration is required--the crash will happen out of the box.