582252 - Memory leaks found by XPCOM_MEM_LEAK_LOG with default Minefield start page

Status: RESOLVED INVALID

(Core :: General, defect)

Description

[Benoit Jacob [:bjacob] (mostly away)]

Attachment: leak log

Steps to reproduce:

1. export XPCOM_MEM_LEAK_LOG=memleaklog
2. start firefox, wait for the start page to finish loading.
3. quit firefox, look at the memleaklog file.

I am using a profile that uses the default Minefield start page.
I have made sure to wait for the page to finish loading ("Done" in the status bar).

Comment 1

[Boris Zbarsky [:bzbarsky]]

I don't get a leak in a current debug Mac build on OS X 10.5 using a clean profile when using the steps from comment 0, or more precisely the following steps:

1)  Compile a clean m-c build.
2)  rm -rf /tmp/test-prof
3)  run |firefox -profile /tmp/test-prof| to make sure that there's a clean
    profile there and that we're not measuring weird first-profile-creation
    issues.
4)  run |env XPCOM_MEM_LEAK_LOG=memleaklog cleanfox -profile /tmp/test-prof| to
    measure leaks.

What's different about your setup?  Is the profile you're using clean?  Any extensions?

Comment 2

[Benoit Jacob [:bjacob] (mostly away)]

Indeed, following your steps, I don't get any leak. I guess then that my profile was 'bad' in some way. Thanks for your time!

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

ah no, wait! It was reusing another firefox instance as we don't pass -no-remote here.

Comment 4

[Benoit Jacob [:bjacob] (mostly away)]

... but indeed, this time with -no-remote and a clean profile, I see no leak.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Might be worth figuring out what about that profile causes leaks... esp. extensions, if any.  That leak output shows you leaking "the world" (DOM windows and everything they contain).

Comment 6

[Benoit Jacob [:bjacob] (mostly away)]

The only add-on I had was Firebug (which I had installed even though it didn't claim to support Minefield). I removed it and that 'fixed' the leaks. Thanks!