Confirmed users
1,067
edits
Firefox3/StatusMeetings/2008-03-11: Difference between revisions
Jump to navigation
Jump to search
Firefox3/StatusMeetings/2008-03-11 (view source)
Revision as of 17:17, 11 March 2008
, 11 March 2008→Platform: issues for next milestone & final ship
| Line 18: | Line 18: | ||
== Platform: issues for next milestone & final ship == | == Platform: issues for next milestone & final ship == | ||
* Memory Usage | * Memory Usage | ||
Here's a leak report from Tomcat (wow!): | |||
New Leak Bugs: | |||
-> Filed 15 leak bugs since last week (alone 12 since Saturday :) with one Leak Regression.(Bug Bug 421150).. | |||
Most of them are triaged by drivers (many thanks Damon) and 5 Bugs are now left on the Nomination List. | |||
For https://bugzilla.mozilla.org/show_bug.cgi?id=421703 i'm not sure if this really blocking. This Leak was found when i run Leak Gauge with the Beta 4 RC2 to test the respinned PGO Build. So its my first Leak Gauge Log/bug, peter/ben/jonas can you take a look here at the leak gauge output Maybe this leak is already fixed ? | |||
https://bugzilla.mozilla.org/show_bug.cgi?id=421835 was found on trunk during hammering (clicking around in the new Add-on Manager). Maybe its also not blocking and more wanted 1.9.x since it was only reproducible in 75 % of the tests. Also i think most of the people use the Add-on Manager only to install something and not to click around :-) | |||
All other nominated bugs are Extension Related. And found also 2 new Extension nsGlobalWindows Leaks. | |||
Blocking Leak Bug List contains 12 P2 Bugs. | |||
Seems with this more and more compatible Firefox 3 Extensions we get also more and more Leak Reports. A little sad are comments like this from irc" a friend of a friend is saying that Firefox 2 uses less memory/cpu than Firefox 3 for him with a few extensions loaded".In this case 4 Extensions were installed and 2 of them are already on my Leak Buglist :-/ seems there is still a lot of work left here... | |||
Will start next week to work with Mark Finkle on Docs and Blog Posts for Extension Devs and AMO Editors (Best Practice, Leak Tests with Leak Gauge etc). | |||
*Extension Leak Bugs:* | |||
Jesse mentioned yesterday that we maybe need a Meta Leak Bug for Extension Leaks. I think for my Leak Project its a little too late and so i think we should keep "my" meta Bug 402335 as Tracking for Leaks I (QA) found, but we maybe should file a new Extension Leak Bug for the Leaks that are found by the AMO-Editor Team ? Actually i know that they have started to use Leak Gauge, but i have no idea where they file the bugs. Any suggestions/thoughts ? | |||
Thats all :-) Will go and find some more leaks now :-) -Tomcat | |||
* X-site XMLHttpRequest | * X-site XMLHttpRequest | ||
* SVG | * SVG | ||