Skip to content

Node.js 12.x need to cherry-pick https://github.com/nodejs/node/pull/37616 #42376

Description

@Brooooooklyn

Version

v12.22.11

Platform

Windows x64/macOS x64/Linux x64

Subsystem

No response

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

Native addon uses napi_wrap crash on Node.js 12x while process exiting.

svg-sprite/svg-sprite#606

Additional information

No response

Activity

  1. yisibl commented on Mar 17, 2022

    @yisibl

    I have written a 100% reproducible case here: yisibl/svg-sprite#3

    > mocha "test/**/*.test.js"
    
      calculateSvgDimensions
        ✔ should return the expected dimensions from 46x46 fixture
    
      1 passing (41ms)
    
    [1]    10147 segmentation fault  npm test
  2. Trott commented on Mar 18, 2022

    @Trott
    Member

    Node.js 12.x support ends in about 6 weeks and it is in maintenance mode where it mostly only gets security fixes. So this may not happen. However, the decision of what goes into releases and when is up to the releasers to let's ping them: @nodejs/releasers

  3. XhmikosR commented on Mar 19, 2022

    @XhmikosR
    Contributor

    @Trott agreed, but it seems the #37616 cherry pick should have happened in the first place :/

    We still support Node.js 12 and probably many projects do too, so it'd be nice if we could have this patch before Node.js 12 EOL :)

  4. mhdawson commented on Mar 25, 2022

    @mhdawson
    Member

    @richardlau I see you having volunteered for likely a final release of 12.x on 2022-04-05, I assume that would be the last opportunity to get something like this in, right?

    @legendecas is going to post the list of related PR's that would also need to be cherry-picked because we believe there are a couple more that would need to go along with this.

  5. richardlau commented on Mar 25, 2022

    @richardlau
    Member

    @richardlau I see you having volunteered for likely a final release of 12.x on 2022-04-05, I assume that would be the last opportunity to get something like this in, right?

    Correct. That is planned to be the last release of Node.js 12.x. I'm planning to put together a release proposal next week to give roughly a week to review.

  6. legendecas commented on Mar 27, 2022

    @legendecas
    Member

    The related PRs of this problem are:

    Manually backported to v14.x (Backport PR: #37802):

    Clean land on v14.x:

    So to v12.x, we may need to backport the above PRs to fix the problem.

  7. richardlau commented on Apr 6, 2022

    @richardlau
    Member

    The backports were released in Node.js 12.22.12.

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

    node-apiIssues and PRs related to Node-API.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions