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)

defect

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox79 --- fixed

People

(Reporter: valentin, Assigned: valentin)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(3 files)

Attached file datarace_stacl..txt

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 ?

Severity: -- → S3
Priority: -- → P2

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
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: