Created attachment 8875655 [details] memory-report_20170607_1639.json.gz Prerequisites - Change the Option menu - When Nightly starts, show a blank page - Allow Nightly to Check for updates but let you choose to install them - Deselect "Automatically update search engines - Disable all of the mozilla lists: - privacy.trackingprotection.enabled - privacy.trackingprotection.pbmode.enabled - privacy.trackingprotection.annotate_channels - browser.safebrowsing.blockedURIs.enabled - plugins.flashBlock.enabled - Disable safe browsing: - browser.safebrowsing.malware.enabled - browser.safebrowsing.phishing.enabled Steps 1. Launch Firefox nightly 2. Move the cursor into the address bar 3. Measure and save memory report (about:memory page) 4. Wait for 24 hours 5. Measure and save memory report (about:memory page) Version: 550a1 (2017-06-06) OS: Windows 7
Attachment #8875656 - Attachment description: memory-report_20170608_1639.json → memory-report_20170608_1639.json.gz
Attachment #8875656 - Attachment filename: memory-report_20170608_1639.json → memory-report_20170608_1639.json.gz
Attachment #8875656 - Attachment mime type: application/json → application/gzip
Attachment #8875655 - Attachment description: memory-report_20170607_1639 → memory-report_20170607_1639.json.gz
Attachment #8875655 - Attachment filename: memory-report_20170607_1639.json → memory-report_20170607_1639.json.gz
Attachment #8875655 - Attachment mime type: application/json → application/gzip
To clarify, you observed increased memory usage over time from the Windows system monitor, right? I compared the two memory reports. There are some Telemetry which are expected. There are 325.01 MB private memory committed which looks like bug 1347909.
Yes, I used the windows system monitor.
Yeah sounds like a dup, but the STR sounds useful.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1347909
Just to let Cynthia know, this is probably the same bug that was reported in a few other dupes bug 1379250 bug 1298905 bug 1357225 bug 1347909 bug 1361016 which was resolved in bug 1377738
You need to log in before you can comment on or make changes to this bug.