On 31-03-16 15:17, Jim Mathies wrote: > On Wednesday, March 30, 2016 at 1:28:18 PM UTC-5, Kyle Huey wrote: >> The other types (TYPE_UI, TYPE_IO, and >> TYPE_MOZILLA_NONMAINUITHREAD) involve varying levels of platform >> specific event loop or API integration that will probably be more >> difficult to untangle. They also won't block my long-term desire to >> build a scheduler for Gecko, so are lower priority. > > We might be able to convert TYPE_MOZILLA_NONMAINUITHREAD to a > TYPE_MOZILLA_NONMAINTHREAD now. This was added for media code which > was (is still?) interacting with native windows on the desktop, > chatting with local devices, and other related native media activity. > It might be overkill now. An audit of what we ended up using here > would tell. The loop isn't troublesome in any way but might be a pain > to convert over to whatever new system you plan to implement.
The bug that introduced the usage is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1060738 We still use this code for WebRTC, although it's in CamerasParent now. I think MediaManager still uses NONMAINUITHREAD as well but it probably doesn't need to anymore, because the camera access got moved outside its thread. -- GCP _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
