Open Bug 1735930 Opened 4 years ago Updated 4 years ago

Investigate making Profiler objects (e.g.: ThreadRegistry, mutexes) outlive static storage, to handle threads outliving the main thread

Categories

(Core :: Gecko Profiler, task, P3)

Product:
Core
Component:
Gecko Profiler
Type:
task

Tracking

()

People

(Reporter: mozbugz, Unassigned)

References

Details

Bug 1734262 shows that some threads outlive main(), and either unregister during/after static destructions (when mutexes, the ThreadRegistry, and maybe other Profiler objects, may have already been destroyed), or never unregister.

It may be good to handle these cases, if only not to crash if such threads try to use the Profiler this late.

This may mean intentionally leaking some objects, but that should be acceptable as they don't have user-visible side-effects on destruction.

(If this happens, we may want to revert the last patch of bug 1734262, which removed the thread registration altogether as a workaround.)

You need to log in before you can comment on or make changes to this bug.