If nsThread::GetEvent waits for events, make it wake up when new events arrive on mIdleEvents as well as mEvents

NEW
Unassigned

Status

()

Core
DOM
P3
normal
a year ago
a year ago

People

(Reporter: farre, Unassigned)

Tracking

48 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Reporter)

Updated

a year ago
Depends on: 1198381
Priority: -- → P3
Not a lot of explanation here.  Is this a super rare occurrence or something?  At face value seems like something we should fix soonish.
Flags: needinfo?(afarre)
This should happen only when idle runnables are dispatched from other threads, and that shouldn't happen yet. Yes, we should fix this soon, or at least add an assertion that idle runnables could be dispatched only from the same thread.
The assertion sounds like a very nice idea if we are relying on that invariant at the moment.
(Reporter)

Comment 4

a year ago
I'll add the assertion along with a commo
Assignee: nobody → afarre
Flags: needinfo?(afarre)
(Reporter)

Comment 5

a year ago
I'll add the assertion along with a comment that it can be removed if/when we start supporting off thread dispatch.
(Reporter)

Comment 6

a year ago
Created Bug 1315187.
(Reporter)

Updated

a year ago
Assignee: afarre → nobody
You need to log in before you can comment on or make changes to this bug.