forked from mirrors/gecko-dev
Bug 1806852 - Use nsThread::GetThreadName in the threads memory reporter. r=xpcom-reviewers,emilio
Differential Revision: https://phabricator.services.mozilla.com/D176191
This commit is contained in:
parent
8e9b6d5099
commit
b92f264caa
1 changed files with 3 additions and 1 deletions
|
|
@ -1488,8 +1488,10 @@ class ThreadsReporter final : public nsIMemoryReporter {
|
||||||
"platform");
|
"platform");
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
|
nsCString threadName;
|
||||||
|
thread->GetThreadName(threadName);
|
||||||
threads.AppendElement(ThreadData{
|
threads.AppendElement(ThreadData{
|
||||||
nsCString(PR_GetThreadName(thread->GetPRThread())),
|
std::move(threadName),
|
||||||
thread->ThreadId(),
|
thread->ThreadId(),
|
||||||
// On Linux, it's possible (but unlikely) that our stack region will
|
// On Linux, it's possible (but unlikely) that our stack region will
|
||||||
// have been merged with adjacent heap regions, in which case we'll
|
// have been merged with adjacent heap regions, in which case we'll
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue