Closed Bug 1539944 Opened 2 years ago Closed 1 year ago

Remove NS_NewThread in favour of NS_NewNamedThread

Categories

(Core :: XPCOM, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: mconley, Assigned: KrisWright)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

We don't use NS_NewThread much these days (I see it only being used in test code as of current mozilla-central), and I think we should probably remove it.

That way, people have to use NS_NewNamedThread, which is better, since it means that we'll have useful names for threads appear in things like the Gecko Profiler.

Blocks: 1537951
Severity: normal → enhancement
Priority: -- → P3
Blocks: 1613440

Gets rid of NS_NewThread. Where it was used in testing, I gave the named threads names relevant to their tests. I didn't name the crash reporter testing threads because the test runnables set their own names as a part of the testing process.

Assignee: nobody → kwright
Status: NEW → ASSIGNED
Flags: needinfo?(kwright)

Relanded ^

Flags: needinfo?(kwright)
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
See Also: → 1614900
See Also: → 1694462
You need to log in before you can comment on or make changes to this bug.