Closed
Bug 1644478
Opened 5 years ago
Closed 5 years ago
Data Race when setting priority for TRR service channel
Categories
(Core :: Networking, defect, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
mozilla79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(3 files)
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=305569607&repo=try&lineNumber=3689
It seems that we have a data race when setting a higher priority for the TRRService channel.
I assume the fix would be to make the priority Atomic.
Since the increased priority didn't actually fix the TRR performance issue should we also remove this code ?
Assignee | ||
Updated•5 years ago
|
Severity: -- → S3
Priority: -- → P2
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
This was done before using a different thread for the TRR channel
and it didn't actually make a difference in performance, so
maybe we should remove this code.
Depends on D78938
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/0d26c935c177
Make nsPipeInputStream::mPriority Atomic r=mayhemer
https://hg.mozilla.org/integration/autoland/rev/2ddc1c822b05
Don't increase priority for TRR service channel r=mayhemer,necko-reviewers
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0d26c935c177
https://hg.mozilla.org/mozilla-central/rev/2ddc1c822b05
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in
before you can comment on or make changes to this bug.
Description
•