Closed Bug 1556109 Opened 6 years ago Closed 6 years ago

[socket-process] shows up as not responding in OSX activity monitor

Categories

(Core :: WebRTC: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: drno, Assigned: bwc)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

When running with the socket process turned on OSX I see in the activity monitor the socket process using CPU and everything works fine. But the activity monitor highlights the process in red and with "not responding" after it's name.

We had exactly the same issue with the RDD process, which got fixed here: https://searchfox.org/mozilla-central/source/dom/media/ipc/RDDParent.cpp#122-125

But I don't know where to apply that code in the socket process.

Byron can you take a look and ask Haik (the author of the patch for RDD) and others how to get this fixed?

Flags: needinfo?(docfaraday)

I'll look into it.

Assignee: nobody → docfaraday
Flags: needinfo?(docfaraday)

Whatever the reason, I am not able to reproduce this bug on my OS X laptop. But, I've attached a patch that should fix it, based on what we did with RDD. Nils, can you try it out?

Flags: needinfo?(drno)

Try looks good.

Yes this fixes the problem locally for me.

Flags: needinfo?(drno)
Pushed by nohlmeier@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/848ef7b322ef Socket process does not have a UI event loop, so disconnect from the window server. r=kershaw
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: