Closed Bug 1283245 Opened 8 years ago Closed 8 years ago

Use js::Mutex and js::ConditionVariable instead of PRLock and PRCondVar in HelperThreads

Categories

(Core :: JavaScript Engine, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla50
Iteration:
50.2 - Jul 4
Tracking Status
firefox50 --- fixed

People

(Reporter: fitzgen, Assigned: fitzgen)

References

Details

Attachments

(1 file)

      No description provided.
Assignee: nobody → nfitzgerald
Blocks: 956899, 1263289
Status: NEW → ASSIGNED
Depends on: 1283229
Whiteboard: [devtools-html]
Iteration: --- → 50.2 - Jul 4
Flags: qe-verify-
Priority: -- → P1
Comment on attachment 8766472 [details] [diff] [review]
Use js::Mutex and js::ConditionVariable instead of PRLock and PRCondVar in HelperThreads

Review of attachment 8766472 [details] [diff] [review]:
-----------------------------------------------------------------

::: js/src/vm/HelperThreads.h
@@ +470,5 @@
>  
>  class MOZ_RAII AutoUnlockHelperThreadState
>  {
> +    // This is only in a Maybe so that we can update the DEBUG-only lockOwner
> +    // thread in the proper order :-/

First, use a period instead of a meh.

Secondly, could we move the owner-tracking code into js::Mutex? It seems like it would simplify a lot of the code in our tree, since all three of them are currently tracking the owner manually. Maybe for a followup.
Attachment #8766472 - Flags: review?(terrence) → review+
Pushed by nfitzgerald@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c62dc1a368c8
Use js::Mutex and js::ConditionVariable instead of PRLock and PRCondVar in HelperThreads; r=terrence
https://hg.mozilla.org/mozilla-central/rev/c62dc1a368c8
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
Depends on: 1284370
Whiteboard: [devtools-html]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: