Closed Bug 1322435 Opened 3 years ago Closed 3 years ago

Consider reducing the number of image decoder threads in the parent process in e10s

Categories

(Core :: ImageLib, defect)

Product:
Core
Component:
ImageLib
Type:
defect
Priority:
Not set

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla53
Tracking Flags:
Tracking Status
firefox53 --- fixed

People

(Reporter: mstange, Assigned: tnikkel)

Details

Attachments

(1 file)

limit 4 threads in parent process
1.56 KB, patch
aosmond
: review+
mstange
: feedback+
Details | Diff | Splinter Review 
Not sure how much they cost, but having 7 mostly unused decoder threads in the process that only renders chrome seems excessive.
Assignee: nobody → tnikkel
Attachment #8817320 - Flags: review?(aosmond)
Attachment #8817320 - Flags: feedback?(mstange)
Comment on attachment 8817320 [details] [diff] [review]
limit 4 threads in parent process

Review of attachment 8817320 [details] [diff] [review]:
-----------------------------------------------------------------

LGTM!
Attachment #8817320 - Flags: review?(aosmond) → review+
Comment on attachment 8817320 [details] [diff] [review]
limit 4 threads in parent process

Yeah four seems fine, thanks
Attachment #8817320 - Flags: feedback?(mstange) → feedback+
Pushed by tnikkel@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d8f60ae71774
Limit the number of image decoding threads we use in the parent process. r=aosmond
https://hg.mozilla.org/mozilla-central/rev/d8f60ae71774
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox53: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in before you can comment on or make changes to this bug.