镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

process.title don't change process name #28945

Description

@CubixSystem
  • Version: v10.16.1
  • Platform: 18.7.0 Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64
  • Subsystem: process

Hello

In v10.16.1

process.title = "test";

stops changing process name

In v10.15.3
All works as expected

Activity

  1. addaleax commented on Aug 2, 2019

    @addaleax
    Member

    /cc @nodejs/platform-macos since on Linux this seems to work

  2. added
    macosIssues and PRs related to the macOS platform.
    on Aug 2, 2019
  3. CubixSystem commented on Aug 2, 2019

    @CubixSystem
    Author

    I use nvm, my steps to reproduce:

    nvm use v10.15.3 && /
    node -e "process.title = 'process.title test'; process.stdin.resume();"

    Screenshot 2019-08-02 at 21 16 21

    nvm use v10.16.1 && /
    node -e "process.title = 'process.title test'; process.stdin.resume();"

    Screenshot 2019-08-02 at 21 16 59

  4. jasnell commented on Aug 2, 2019

    @jasnell
    Member

    Can I ask you to check to see if the current Node.js 12.x release works? Like to see if this regression is specific to 10.x or not.

  5. Trott commented on Aug 2, 2019

    @Trott
    Member

    Can I ask you to check to see if the current Node.js 12.x release works? Like to see if this regression is specific to 10.x or not.

    I can reproduce the issue in 12.0.0 and 12.7.0. Like original reporter, I'm seeing the problem in 10.16.1 but not in 10.15.3. I also see the problem in 10.16.0.

  6. added
    confirmed-bugIssues and PRs for confirmed bugs.
    processIssues and PRs related to the process subsystem.
    on Aug 2, 2019
  7. Trott commented on Aug 2, 2019

    @Trott
    Member

    8.16.0 does not have the bug.

    So, to summarize for supported release lines on macOS:

    • All 12.x are affected.
    • 10.16.0 and newer are affected. 10.15.3 and earlier are not affected.
    • All 8.x are not affected.
  8. richardlau commented on Aug 2, 2019

    @richardlau
    Member

    Sounds like it could be libuv related based on the Node.js versions affected. Node.js 10.16.0 bumped libuv from 1.23.2->1.28.0.

  9. jasnell commented on Aug 2, 2019

    @jasnell
    Member

    Windows also appears to work as expected

  10. richardlau commented on Aug 3, 2019

    @richardlau
    Member
  11. Trott commented on Aug 3, 2019

    @Trott
    Member

    git bisect confirms that this bug was introduced with the upgrade to libuv 1.24.0 in 9cef7b8. I suppose the thing to do is open an issue in the libuv repository. @nodejs/libuv

  12. bnoordhuis commented on Aug 3, 2019

    @bnoordhuis
    Member

    I can confirm that libuv/libuv@00c6b16 is responsible (but don't ask me why.) I've opened a revert in libuv/libuv#2405.

  13. 13 remaining items

  14. coreybutler commented on Jul 9, 2020

    @coreybutler
    Member

    This appears to be an issue again in 14.x.x. Works in 13.x.x.

    cc @cjihrig @addaleax @bnoordhuis @Trott

  15. bnoordhuis commented on Jul 9, 2020

    @bnoordhuis
    Member

    @coreybutler Can you file a new issue and link back to this one?

  16. coreybutler commented on Jul 9, 2020

    @coreybutler
    Member

    @bnoordhuis sure, ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmed-bugIssues and PRs for confirmed bugs.libuvIssues and PRs related to the libuv dependency or the uv binding.macosIssues and PRs related to the macOS platform.processIssues and PRs related to the process subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions