On 2017-04-07 9:11 AM, Ehsan Akhgari wrote:
- DOM. In the DOM team there are several plans and projects under way
which will hopefully bring various performance improvements to the
browser. Probably the largest one is the upcoming plans for cooperative
scheduling of tasks, which will allow us to interrupt currently executing
JavaScript on background pages in order to service tasks belonging to
foreground pages. You may have seen patches landing as part of a large
effort to label all of our runnables
<https://bugzilla.mozilla.org/show_bug.cgi?id=1321812>. This is needed
so that we can identify how to schedule tasks cooperatively.
Are the bugs to label runnables good for volunteer contributors? Or
would it be fastest for a DOM expert or engineers from each module to
rip through the open bugs? Do we need to ask module owners to prioritize
these bugs? :)
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1321812&hide_resolved=1
According to a searchfox search for unlabeled runnable calls (using the
function names billm provided), there are still over 800 unlabeled
runnables:
http://searchfox.org/mozilla-central/search?q=%5CbNS_DispatchTo(Main%7CCurrent)Thread+*%5C(&case=true®exp=true&path=
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
