Some interpretation and general comments below. loading home.netscape.com TestGtkEmbed uses ~53% less memory than Mozilla. Note that the two applications are *not* functionally equivelent from a UI/feature set standpoint. With that said, the summarization below of css, js, xul, and xbl is still interesting.
For a more real comparison of the cost of XUL front ends, we'd need to build a TestGtkEmbed UI equiv in XUL. Suresh Duddi wrote: >Notes >------------------------------------------------------------------------ >- xpcom is too high. It will go down once we have an embedded package. > we already have one (manifest based). please "gmake" in mozilla/embedding/config >TestGtkEmbed >- Allocations live post startup of home.netscape.com >All [ 4,257,896 size, 100.0%, 45,387 allocations ] >css [ 275,592 size, 6.5%, 4,661 allocations ] >js [ 158,800 size, 3.7%, 2,526 allocations ] >xbl [ 117,296 size, 2.8%, 1,994 allocations ] >xul [ 21,128 size, 0.5%, 263 allocations ] >js-catchall [ 21,056 size, 0.5%, 306 allocations ] > css, js, xbl, xul (as currently categorized) = 14% >Mozilla >- Default Profile loading home.netscape.com. Allocations alive post startup >All [ 9,087,008 size, 100.0%, 111,978 allocations ] >js [ 1,373,312 size, 15.1%, 18,738 allocations ] >xbl [ 1,119,176 size, 12.3%, 19,231 allocations ] >xul [ 866,808 size, 9.5%, 13,861 allocations ] >css [ 790,032 size, 8.7%, 14,694 allocations ] >js-catchall [ 129,976 size, 1.4%, 2,143 allocations ] > css, js, xbl, xul (as currently categorized) = 47%
