341099 - Microsummaries cause memory leak and slowdown when no network connection is present

Status: RESOLVED FIXED

(Firefox Graveyard :: Microsummaries, defect, P2)

Description

[Paul Stone]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060609 BonEcho/2.0a3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060609 BonEcho/2.0a3

I'm a dialup user, and often after disconnecting and being away from the computer for a while I've returned to find that Firefox has leaked memory and is somewhat slower. Most noticeable is jerkiness when scrolling over links (I have smoothscroll turned on). 


Reproducible: Always

Steps to Reproduce:
1. Have one or more microsummaries on your bookmark toolbar (I have the Word of the Day one from http://www.melez.com/mozilla/microsummaries/generators/)
2. Restarting the browser after adding the microsummary may be necessary.
2. Disable your network connection.
3. Leave computer for about an hour

Actual Results:  
Return to find Firefox has leaked memory and is slower, as described above. After about two hours I had FF go from about 30MB to 110MB memory usage, but the slowdown is what made me notice this.

Expected Results:  
No memory leak

I can only reproduce this when I have a microsummary present AND I'm disconnected from the net. It is reproducible in safe mode. When I'm disconnected, the 'Work Offline' menu item is NOT checked. I know there has been an Auto Offline feature added, I don't know how that works or if it is related.

Comment 1

[Myk Melez [:myk] [@mykmelez]]

The fix I'm working on for bug 339543 might also fix this.

Comment 2

[Mike Connor [:mconnor]]

myk, can you reproduce this?

Comment 3

[Myk Melez [:myk] [@mykmelez]]

I haven't reproduced this yet, but I'm going to leave Firefox running without a network connection overnight tonight to see if I can.  Then I'll try again with my patch for bug 339543 applied.

Comment 4

[Myk Melez [:myk] [@mykmelez]]

Confirmed.  Also, I've confirmed that the fix for bug 339543 also fixes this bug.  Making this one depend on that one.

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Fixed by the checkin for bug 339543.