Closed Bug 51074 Opened 26 years ago Closed 25 years ago

ProxyObject implementation seriously leaks memory

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: egger, Assigned: dougt)

Details

Now that memprof (from the GNOME project) finally works with Mozilla I did a little profiling. I started mozilla and visited www.mozilla.org then the Seamonkey tinderbox and then some of the CVS logs. However which sites are visited doesn't matter. The memcache was turned off in the preferences. It turned out that the nsProxyObject::Post function allocates one event per call using PL_InitEvent which are not freed again at some point. The leak profile shows that event structures sum up to about 700KB after 4 minutes of browsing whereas each structure has either 20 or 84 bytes on Linux-x86. What makes me worry a bit is that mozilla and companions have around 150K open allocations while running it in one window on the mozilla homepage. That means that mozilla does millions of allocations in a few minutes which is a little bit performance critical and the general number of allocations leads to memory hogging because of the allocation overhead.
Is this still a problem in the latest nightly builds?
setting bug status to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
At least on i386 this leak seems to have vanished, I'm using a nightly from short after M18 right now. I still see a few bigger leaks in the gif code and smaller ones in the Java code but you can probably close that bug.
This is unrelated to the Necko cache. ProxyObject is in XPCOM. Doug, who should get this?
Assignee: neeti → dougt
Component: Networking: Cache → XPCOM
marking as invalid based on Daniel's last comments. I would be surprized if these allocations were not being freed. I do agree though, that we should probably cache a few of these PL_Events so that we don't have to malloc/free then so much. I actually have to do this for necko, and I could borrow the code from their and add it to the xpcom/proxy stuff too. thanks
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
qa to xpcom, based on doug's comments.
QA Contact: tever → scc
You need to log in before you can comment on or make changes to this bug.