Currently every SwCompositor has a SwCompositeThread associated with it. Most of these threads are parked and not doing much though when the window is not active. We might want to investigate either stuffing these into a limited size thread-pool. Alternatively, we might want to just limit the size of the SwCompositeThread's stack, since all the thread does is call Composite in a loop, and a large stack for each thread of these threads is wasteful.
Bug 1670328 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently every SwCompositor has a SwCompositeThread associated with it. Most of these threads are parked and not doing much though when their respective windows are not active. We might want to investigate stuffing these into a limited size thread-pool. Alternatively, we might want to just limit the size of the SwCompositeThread's stack, since all the thread does is call Composite in a loop, and a large stack for each thread of these threads is wasteful.