With Just Weave and Nightly tester tools, leak-gauge.pl shows memory leak.

RESOLVED INCOMPLETE

Status

Cloud Services
General
RESOLVED INCOMPLETE
10 years ago
9 years ago

People

(Reporter: Matt, Assigned: thunder)

Tracking

({mlk})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007122705 Minefield/3.0b3pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007122705 Minefield/3.0b3pre ID:2007122705

I visited gmail.com, google.com and www.mozilla.org/projects/minefield, however I don't think the webpages were the cause. Upon uninstalling weave and closing the browser, DOM leaks were gone. I DO NOT have user information entered into weave, that could be the cause but it probably shouldn't leak at this point anyway. 

This is my first time making a bug report, let alone a memory leak bug report, I'm re-reading DBarron's post on making good memory leak bug reports as I'm writing this but will update it if I realized I missed something. Be gentle and let me know if i need to include more info.

Heres the results of leak-gauge.pl analyzing the log:

Leaked inner window 1525070 (outer 14ad9c0) at address 1525070.
 ... with URI "about:blank".
Leaked outer window 14ad9c0 at address 14ad9c0.
Summary:
Leaked 2 out of 22 DOM Windows
Leaked 0 out of 64 documents
Leaked 0 out of 9 docshells



Reproducible: Always

Steps to Reproduce:
1. Install Weave
2. Start firefox in cmd using (make changes of course if your directory for firefox is different):
set NSPR_LOG_MODULES=DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5
set NSPR_LOG_FILE=C:/Program Files/Minefield/nspr.log
start "Firefox" /wait "C:\Program Files\Minefield\firefox.exe"
3. Analyze using leak-gauge.pl after closing firefox using:
perl "C:\Program Files\Minefield\leak-gauge.pl" > "C:\Program Files\Minefield\nspr_leaks.log"
4. See results of memory leak
5. ...
6. Profit?
Actual Results:  
Leaked inner window 1525070 (outer 14ad9c0) at address 1525070.
 ... with URI "about:blank".
Leaked outer window 14ad9c0 at address 14ad9c0.
Summary:
Leaked 2 out of 22 DOM Windows
Leaked 0 out of 64 documents
Leaked 0 out of 9 docshells

Expected Results:  
Leaked 0 out of 22 DOM Windows

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007122705 Minefield/3.0b3pre ID:2007122705

Extensions:
DOM Inspector 1.9b3pre
Nightly Tester Tools 1.3b3

and of course Weave v0.1 (before I uninstalled it)
(Reporter)

Updated

10 years ago
Summary: With Just Weave and Nightly tester tools, leak-gauge.pl picks up memory leak. → With Just Weave and Nightly tester tools, leak-gauge.pl shows memory leak.
(Assignee)

Comment 1

10 years ago
Thanks for the report, Matt.
Assignee: nobody → thunder
(Reporter)

Updated

10 years ago
Keywords: mlk
(Assignee)

Comment 2

10 years ago
Does this still happen?  A lot has changed since december, could you re-test?
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE

Comment 3

10 years ago
I turned on weave right after installing FF 3.0 release.  After doing the sync and going through 1-2 websites, FF grew from 80mb of memory usage to 120 and continued to climb until I had to kill the process.  It was also using 100% of the cpu.  

This is as of 2 days ago with 0.1.30 and 3.0 release.

The only thing different from default is, in configuring weave I did turn on all the sync options.  I had 3 clients all installed with weave and subscribed to the same account.

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.