Closed
Bug 1231482
Opened 9 years ago
Closed 9 years ago
PROFILER_MARKER creates markers but they don't show up in cleopatra
Categories
(Core :: Gecko Profiler, defect)
Tracking
()
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox45 | --- | affected |
People
(Reporter: kats, Unassigned)
References
Details
Attachments
(1 file)
|
1.98 MB,
text/plain
|
Details |
I added a PROFILER_MARKER("Scroll event") in ScrollFrameHelper::FireScrollEvent() and grabbed a profile that hit that code. However cleopatra didn't show the marker. The raw JSON does have the event (see attached file) so I presume this is an issue in cleopatra.
|
||
Comment 1•9 years ago
|
||
Your last marker is at t=14909ms. The profiler drops samples that go out of range of the buffer. The UI also filters out samples in the timeline that occur before other timeline start. In your case you're sample is in the profile but it's filtered out by the UI. I'd suggest grabbing a profile where your marker is in the relevant area or profiling just that thread.
|
|
||
Comment 2•9 years ago
|
||
Going with 'INVALID' since the marker do work but I can admit that's it confusing. Let me know if you have any questions.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
|
Reporter | |
Comment 3•9 years ago
|
||
I don't understand this but I can show you in person. The marker was definitely issued within the period that I profiled.
You need to log in
before you can comment on or make changes to this bug.
Description
•