Closed
Bug 1354189
Opened 8 years ago
Closed 8 years ago
LUL can't unwind past pthread_cond_wait
Categories
(Core :: Gecko Profiler, defect)
Core
Gecko Profiler
Tracking
()
RESOLVED
DUPLICATE
of bug 1354546
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: mstange, Unassigned)
References
(Blocks 1 open bug)
Details
Example profile: https://perfht.ml/2p5zfLA
STR:
1. Be on stock Ubuntu Linux, other Linux distributions probably work as well.
2. Turn on the profiler.
3. Navigate to https://public.etherpad-mozilla.org/p/wr-plan
4. Take a profile.
5. Look at the content process that's shows a lot of jank.
6. See that the stack during most of the waiting is really short:
__pthread_unwind_next
__pthread_mutex_unlock
pthread_cond_wait
0x411bae
PRemoteSpellcheckEngine::Msg_Check
Startup::XRE_InitChildProcess
(root)
This shows that we were not able to unwind past pthread_cond_wait - we found a garbage frame "0x411bae" instead, aborted C++ stack frame unwinding, and fell back to the pseudostack.
Comment 1•8 years ago
|
||
I think this is a sub-case of bug 1354546, and so has now been fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•8 years ago
|
||
Confirmed, this is working now. Example profile: https://perfht.ml/2oal247
It looks like perf.html wasn't able to assign a library to the 0x40xxxx range, though, and consequently didn't symbolicate them.
Reporter | ||
Comment 3•8 years ago
|
||
And that's because the main executable doesn't have a debugName or a breakpadId in the sharedLibraries list. Filed bug 1358360.
You need to log in
before you can comment on or make changes to this bug.
Description
•