You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PWAs on macOS differ from other applications in how they show up in Activity Monitor.app. Other apps (and even Safari Web Apps) get listed as a full "Application" so that their energy usage can be monitored, and so their hierarchy of processes is kept sorted correctly. Firefox PWAs do not get this "Application" listing.
This prevents the application from showing up in the Energy tab when sorted by Applications, and it also causes issues for apps like iStat Menus, which end up showing loader as the process rather than the application with the correct name/icon.
Steps to Reproduce
Create and run a Firefox PWA
Open Activity Monitor.app from Utilities
Go to the Energy tab, then View -> Applications in the last 12 hours
Observe that the Firefox PWA does not get listed
Additional Information
I think this is related to the fact that other apps have an application bundle at the top of the process hierarchy. Firefox PWAs have the loader process as the top level (i.e., directly beneath launchd).
Environment
Operating system: macOS 14.4.1
System architecture: Apple Silicon
Installation method: Homebrew
PWAsForFirefox extension version: 2.12.0
PWAsForFirefox native version: 2.12.0
PWAsForFirefox runtime version: 125.0.3
Firefox version: 125.0.3
The text was updated successfully, but these errors were encountered:
Description
PWAs on macOS differ from other applications in how they show up in Activity Monitor.app. Other apps (and even Safari Web Apps) get listed as a full "Application" so that their energy usage can be monitored, and so their hierarchy of processes is kept sorted correctly. Firefox PWAs do not get this "Application" listing.
This prevents the application from showing up in the Energy tab when sorted by Applications, and it also causes issues for apps like iStat Menus, which end up showing
loader
as the process rather than the application with the correct name/icon.Steps to Reproduce
Additional Information
I think this is related to the fact that other apps have an application bundle at the top of the process hierarchy. Firefox PWAs have the
loader
process as the top level (i.e., directly beneathlaunchd
).Environment
The text was updated successfully, but these errors were encountered: