Closed
      
        Bug 1646803
      
      
        Opened 5 years ago
          Closed 5 years ago
      
        
    
  
The parent process' main thread doesn't have a name
Categories
(Core :: XPCOM, enhancement)
        Core
          
        
        
      
        
    
        XPCOM
          
        
        
      
        
    Tracking
()
        RESOLVED
        FIXED
        
    
  
        
            mozilla79
        
    
  
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed | 
People
(Reporter: florian, Assigned: florian)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
In about:processes, the main thread of the parent process doesn't have a name and is shown as '???'.
For child processes, the MainThread name is set at https://searchfox.org/mozilla-central/rev/5e6c7717255ca9638b2856c2b2058919aec1d21d/toolkit/xre/nsEmbedFunctions.cpp#340
We need to do something equivalent for the parent.
| Comment 1•5 years ago
           | ||
I think the equivalent function for the parent process is XRE_InitParentProcess().
| Assignee | ||
| Comment 2•5 years ago
           | ||
I tried adding NS_SetCurrentThreadName("MainThread"); in XRE_InitParentProcess right after the NS_SetMainThread(); line but that didn't change the name in about:processes.
When I add NS_SetCurrentThreadName("MainThread"); in XRE_main the name is displayed in about:processes.
| Assignee | ||
| Comment 3•5 years ago
           | ||
| Updated•5 years ago
           | 
Assignee: nobody → florian
Status: NEW → ASSIGNED
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9f8a59996994
name the parent process main thread, r=froydnj.
|   | ||
| Comment 5•5 years ago
           | ||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
          status-firefox79:
          --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
| Updated•5 years ago
           | 
QA Whiteboard: [qa-79b-p2]
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•