Closed
Bug 1039577
Opened 10 years ago
Closed 10 years ago
CrashReporter::OOPInit should be multithread-safe
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
Attachments
(1 file)
3.48 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
Currently CrashReporter::OOPInit assumes that it's called from the main thread, but in the case of GMP plugins that's no longer true. The patch I will attach shortly synchronously proxies the work to the main thread. I believe that the rest of the code is already threadsafe; it's used from the IPC thread and others already.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8456971 -
Flags: review?(ted)
Comment 2•10 years ago
|
||
Comment on attachment 8456971 [details] [diff] [review] bug1039577-OOPInit Review of attachment 8456971 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/crashreporter/nsExceptionHandler.cpp @@ +2561,1 @@ > if (OOPInitialized()) There shouldn't be any risk of races here if this is called from multiple background threads because they'll be serialized on the main thread, right?
Attachment #8456971 -
Flags: review?(ted) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Correct, the proxy to the main thread is the inherent synchronization.
Assignee | ||
Comment 4•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/fcb0e9c6c148
Target Milestone: --- → mozilla33
Assignee | ||
Updated•10 years ago
|
QA Whiteboard: [qa-]
Updated•10 years ago
|
Iteration: --- → 33.3
https://hg.mozilla.org/mozilla-central/rev/fcb0e9c6c148
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Flags: firefox-backlog+
You need to log in
before you can comment on or make changes to this bug.
Description
•