Closed
Bug 405542
Opened 17 years ago
Closed 16 years ago
Ts regression on boxset after software update landing
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: samuel.sidler+old, Unassigned)
References
()
Details
(Keywords: perf, regression)
After bug 185436 was landed, there was a noticeable Ts regression. It was about 25-30ms. We should see what's causing it and if we can fix it.
Flags: camino1.6?
Keywords: regression
MainMenu.nib? We're now 1000ms faster on boxset than back then (thanks to Gecko improvements), so the effects have been negated, whatever we decide to do here.
Comment 2•16 years ago
|
||
-ing for 1.6; a minor Ts regression certainly isn't critical.
Flags: camino1.6? → camino1.6-
Per mento in this morning's meeting, this is more-or-less expected in shared builds: [12:37pm] mento: i think that the problem is that dyld's workload is just plain heavier with the shared build [12:37pm] mento: it's not really a growl or sparkle or framework problem [12:37pm] mento: it's a huge symbol table to resolve problem that has just gotten huger
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Depends on: 556428
You need to log in
before you can comment on or make changes to this bug.
Description
•