Follow up work from bug 1060738 - according to jesup: (In reply to Randell Jesup [:jesup] from comment #63) > Note: The reason the Try in comment 32 failed was because > MediaEngineDefault.cpp uses nsITimers on MediaManager thread to generate > fake audio/video; these could easily be swapped or spun off to another > thread. If we can remove reliance on xpcom events, we can stop using franken message loop types TYPE_MOZILLA_NONMAINTHREAD (mac, linux) / TYPE_MOZILLA_NONMAINUITHREAD (win) and instead use just TYPE_DEFAULT/TYPE_UI.

Sending this back to Maire.

Is this resolved? If not, what are the issues remaining?

Sorry for sitting on this, but I don't fully comprehend this improvement request. A quick look shows the things mentioned in comment 0 is still in use: http://mxr.mozilla.org/mozilla-central/search?string=TYPE_MOZILLA_NONMAINTHREAD Deflecting to jimm to answer.

Are we still relying on xpcom for events on the media threads in media code? See bug 1060738, comment 39.

Not a required change, obviously things are working as is.

Mass change P3->P4 to align with new Mozilla triage process.