Closed
Bug 1666303
Opened 5 years ago
Closed 2 years ago
Remove NS_SetCurrentThreadName Android workaround, which is no longer necessary
Categories
(Core :: XPCOM, task)
Tracking
()
RESOLVED
FIXED
116 Branch
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: mstange, Assigned: mak)
References
Details
Attachments
(1 file)
Bug 1541282 added a workaround to NS_SetCurrentThreadName() due to an NSPR bug. The NSPR bug (bug 1541216) is now fixed, and the fix made it into mozilla-central in bug 1562330.
So it should be possible to remove the workaround now.
|
Assignee | |
Comment 1•2 years ago
|
||
The workaround is no longer necessary because NSPR has been fixed.
This allows to use PR_GetThreadName that otherwise returns an empty string.
|
||
Updated•2 years ago
|
Assignee: nobody → mak
Status: NEW → ASSIGNED
Pushed by mak77@bonardo.net:
https://hg.mozilla.org/integration/autoland/rev/8ea07e3a172f
Remove NS_SetCurrentThreadName Android workaround. r=xpcom-reviewers,nika
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox116:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•