Closed Bug 14511 Opened 26 years ago Closed 26 years ago

[PAINTING] Menu items painted thrice each when menu activated

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: shaver, Assigned: pavlov)

References

Details

(Whiteboard: [PDT+] NOV-18 Reporter/owner to verify)

When you select the File menu, for example, we paint the anonymous content of each menu frame three times. I'll try and get stack traces to show the source of the paints.
Blocks: 14469
Severity: normal → critical
Target Milestone: M11
Welcome to the chofmann family.
I don't know what that last comment means. Why is this marked critical severity? That is reserved for crash, data loss and severe leaks. This seems like neither, I can't even see it in the opt bits.
Severity: critical → major
I'll step it down to major, but I think this is likely indicative of a larger multiple-repaint issue. (The comment referred to the fact that this, like all other excessive-paint bugs, is a dependency for 14469, chofmann's tracking bug.)
Assignee: trudelle → pavlov
Priority: P3 → P4
Target Milestone: M11 → M12
Major loss of function? That's still way overblown, but DP showed similar repainting to me today, and the current behavior is disgusting from an efficiency standpoint. Is a debug build needed to see the problem? assigning to pavlov as p4 for m12, cc saari.
Whiteboard: [PDT+]
Putting on [PDT+] radar.
Status: NEW → ASSIGNED
Summary: Menu items painted thrice each when menu activated → [PAINTING] Menu items painted thrice each when menu activated
mass-moving all m12 bugs to m13
Priority: P4 → P3
Target Milestone: M13 → M12
Required for Dogfood??? I don't see how, but I'm sick of arguing. P3 for M12
I don't know what example dp showed you, but bugzilla query is an excellent example. Go to http://bugzilla.mozilla.org/query.cgi. I counted at least five repaintings, each one being different, making the whole experience of visiting that page very disconcerting.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
FIXED
Whiteboard: [PDT+] → [PDT+] NOV-18 Reporter/owner to verify
If this can only be seen in a debug build could the owner or reporter please verify? Otherwise could you provide some insight as to what to look for in an opt build?
Status: RESOLVED → VERIFIED
marking VERIFIED in absence of any evidence to the contrary
You need to log in before you can comment on or make changes to this bug.