Closed
Bug 1781761
Opened 2 years ago
Closed 2 years ago
PROFILER_MARKER_TEXT("ThemeChanged", ...) could now be untyped instead
Categories
(Core :: Layout, task, P3)
Core
Layout
Tracking
()
RESOLVED
FIXED
106 Branch
| Tracking | Status | |
|---|---|---|
| firefox106 | --- | fixed |
People
(Reporter: mozbugz, Assigned: kshampur, Mentored)
References
Details
Attachments
(1 file)
Bug 1670051 added a MARKER_TEXT(..., MarkerStack::Capture(), ""_ns) (notice the empty text), because of bug 1670046 that prevented stack-capture from untyped markers.
But now that bug 1670046 has been fixed, we could change the text marker into an untyped marker.
(Thank you Florian for noticing it.)
|
Reporter | |
Updated•2 years ago
|
Mentor: gsquelart
|
Assignee | |
Updated•2 years ago
|
Assignee: nobody → kshampur
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•2 years ago
|
||
This patch is for adding an untyped marker for when a theme change occurs. Previously we could not get a payload from untyped markers but now we can.
|
||
Updated•2 years ago
|
Attachment #9293373 -
Attachment description: WIP: Bug 1781761 - Change Marker to Untyped for when ThemeChanged is called in the parent process. r?gerald → Bug 1781761 - Change Marker to Untyped for when ThemeChanged is called in the parent process. r?gerald
Pushed by kshampur@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/046874b9811a Change Marker to Untyped for when ThemeChanged is called in the parent process. r=gerald
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•