Closed
Bug 153456
Opened 23 years ago
Closed 23 years ago
RealizePalette causes performance problems
Categories
(Core Graveyard :: GFX, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0.1
People
(Reporter: kmcclusk, Assigned: dcone)
Details
(Keywords: topembed+, Whiteboard: [adt2])
Attachments
(1 file)
|
1.07 KB,
patch
|
kmcclusk
:
review+
waterson
:
superreview+
|
Details | Diff | Splinter Review |
The RealizePalette call in nsRenderingContextWin::CopyOffScreenBits is expensive
and it does not seem to be necessary. It causes performance issues for some
Gecko based applications running in 8-bit display mode.
| Reporter | ||
Updated•23 years ago
|
| Assignee | ||
Comment 1•23 years ago
|
||
If you apply this patch (taking out the RealizePalette() call in the
CopyOffScreenBits seems we play nicer with embedded applications. Seems that
RealizePalette is called everytime the copy from the offscreen buffer goes to
the front which is expensive..
and can timeout the embedded aplications. The RealizePalette() is called
alreadywhen the nsRenderingContext is constructed and when the pixels are
locked. I just commented out the one call to RealizePalette until I can
completly fix
this correctly. I opended a bug (#153367) for fixing the palettes once and for
all and commented in the source. I am trying to make this as small a risk as
possible. I tested with my build for a day using 256 colors and playing with
apps that mess with the palette. I also have a utility that looks at the
system palette while I did that. No new bugs appeared.. although I did notice
some bugs that were already there. My point is that nothing got worse.
Performance did improve.
| Reporter | ||
Comment 2•23 years ago
|
||
Comment on attachment 88696 [details] [diff] [review]
Patch to take out the realizepalette from the bitblit copy
r=kmcclusk@netscape.com
Attachment #88696 -
Flags: review+
Comment 3•23 years ago
|
||
Comment on attachment 88696 [details] [diff] [review]
Patch to take out the realizepalette from the bitblit copy
sr=waterson
Attachment #88696 -
Flags: superreview+
| Assignee | ||
Comment 4•23 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 5•23 years ago
|
||
We need to get this onto the Mozilla 1.01 branch as well.
Don : Can you please send a note to ADT/Drivers for branch checkin approval..thanks
Keywords: adt1.0.1
| Reporter | ||
Updated•23 years ago
|
Whiteboard: [adt2]
Comment 6•23 years ago
|
||
please checkin to the 1.0.1 branch. once there, remove the "mozilla1.0.1+"
keyword and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1+
Comment 7•23 years ago
|
||
adding adt1.0.1+. Please check into the branch asap.
Comment 8•23 years ago
|
||
Patch checked in to the 1.01 branch (by Dcone)
Keywords: mozilla1.0.1+ → fixed1.0.1
Comment 9•23 years ago
|
||
Not sure how QA can verify this one. Need to put verified1.0.1 in keyword field
when verified on branch.
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•