process.title value is not respected on macOS (14.x.x+) #34280
Comments
|
The name is changed (you can verify with |
|
@devsnek ah yes, I do see it with It seems to me that the most common process display tools (like Activity Monitor) should either be supported in Node, or the documentation should have a note to help folks understand why it doesn't display, especially since there are differences between Node releases. Just for reference, node-mac has pretty much "just worked" in Activity Monitor for several years using I can close this issue and open a documentation issue instead, if documentation is a better direction. |
Can you post the output of FWIW, I'm fairly sure certain changes in libuv are responsible, probably libuv/libuv@6e3e422c. If that's the case it's trading a minor regression for a big one and this is the new status quo unless someone figures out a workaround. |
|
Darwin iMac.local 19.5.0 Darwin Kernel Version 19.5.0: Thu Apr 30 18:25:59 PDT 2020; root:xnu-6153.121.1~7/RELEASE_X86_64 x86_64 |
|
fwiw i don't observe any version of node (10 through 14) changing the title in activity monitor. |
|
Libuv's Activity Monitor integration was last tested on macos 10.14. Apple has a habit of breaking the interface with every new release so it's quite possible that it no longer works. I'm not planning to investigate and I'm reluctant to take patches because every change to that subsystem seems to cause regressions, just check out |
|
Given the history and the unstable nature of Apple's releases, perhaps it's better to just document/cite this as a known behavior and move on. Thoughts? |
|
@coreybutler Sounds reasonable. Want to open a PR? |
|
Yeah, I can do that. |
Many users assume the act of assigning a value to `process.title` will update the name of their application in apps like macOS Activity Monitor or Windows Services Manager. This has worked in the past, but fails in some versions of Node.js. Ultimately developers are left confused, especially when it works in one version of Node.js and not another. Given the recurring nature and complexity of the underlying problem, it does not seem like a resolvable problem. This note clarifies the source of the problem, sets developer expectations. Refs: #28945 PR-URL: #34557 Fixes: #34280 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Many users assume the act of assigning a value to `process.title` will update the name of their application in apps like macOS Activity Monitor or Windows Services Manager. This has worked in the past, but fails in some versions of Node.js. Ultimately developers are left confused, especially when it works in one version of Node.js and not another. Given the recurring nature and complexity of the underlying problem, it does not seem like a resolvable problem. This note clarifies the source of the problem, sets developer expectations. Refs: #28945 PR-URL: #34557 Fixes: #34280 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Many users assume the act of assigning a value to `process.title` will update the name of their application in apps like macOS Activity Monitor or Windows Services Manager. This has worked in the past, but fails in some versions of Node.js. Ultimately developers are left confused, especially when it works in one version of Node.js and not another. Given the recurring nature and complexity of the underlying problem, it does not seem like a resolvable problem. This note clarifies the source of the problem, sets developer expectations. Refs: #28945 PR-URL: #34557 Fixes: #34280 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Many users assume the act of assigning a value to `process.title` will update the name of their application in apps like macOS Activity Monitor or Windows Services Manager. This has worked in the past, but fails in some versions of Node.js. Ultimately developers are left confused, especially when it works in one version of Node.js and not another. Given the recurring nature and complexity of the underlying problem, it does not seem like a resolvable problem. This note clarifies the source of the problem, sets developer expectations. Refs: #28945 PR-URL: #34557 Fixes: #34280 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Rich Trott <[email protected]>
processWhat steps will reproduce the bug?
process.title = "test"How often does it reproduce? Is there a required condition?
This appears in all 14.x.x releases. It does not appear in 13.x.x (I tested with 13.5.0)
What is the expected behavior?
The process name should be
test, which is typically reflected in the Activity Monitor on macOS.What do you see instead?
The process name is always
nodeAdditional information
This appears to be a regression of #28945.
The text was updated successfully, but these errors were encountered: