1. posterid:3617156
  2. Messages

Re: node 12 on dunfell memory leaks

Martin Jansa
 

> Is there any reason why dunfell would be stuck at node 12 even though it’s unsupported by node?

node 12 EOL is 2022-04-30 according to https://nodejs.org/en/about/releases/

only security fixes and small bugfix releases are normally backported to stable branches, upgrading node from 12 to 14 is very far from it.

If you need different version, then backport it in different layer. There was also https://github.com/imyller/meta-nodejs which provided multiple version, but this layer wasn't updated for very long time.

On Tue, Oct 26, 2021 at 3:44 PM David Turgeon <david.turgeon@...> wrote:
I’ve noticed issues with node 12 on dunfell memory leaking.  I got around the problem by using a node 14 prebuild which caused the memory leak to go away.

It would be nice to use a shared library though and customize node as yocto currently does for other versions and since node12 has problems with memory leaks anyway it would be nice to upgrade it to
node 14.  I’ll continue to look into why I’m having issues building node 14 by porting the changes.  Currently the issue isn’t very descriptive to me…
rdepends upon non-existent task do_package_write_ipk

Is there any reason why dunfell would be stuck at node 12 even though it’s unsupported by node?

---------- Forwarded message ---------
From: Dave Turgeon <Dave.Turgeon@...>
Date: Mon., Oct. 25, 2021, 1:10 p.m.
Subject: FW: node 12 on dunfell memory leaks
To: david.turgeon@... <david.turgeon@...>


 

 

Dave Turgeon

Embedded Software Developer

IRD (International Road Dynamics)

Ph: (306) 653-9653

 

This E-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this E-mail message immediately.

 

From: Dave Turgeon
Sent: October 25, 2021 1:10 PM
To: 'openembedded-devel@...' <openembedded-devel@...>
Subject: node 12 on dunfell memory leaks

 

I’ve noticed issues with node 12 on dunfell memory leaking.  I got around the problem by using a node 14 prebuild which caused the memory leak to go away.

It would be nice to use a shared library though and customize node as yocto currently does for other versions and since node12 has problems with memory leaks anyway it would be nice to upgrade it to
node 14.  I’ll continue to look into why I’m having issues building node 14 by porting the changes.  Currently the issue isn’t very descriptive to me…
rdepends upon non-existent task do_package_write_ipk

Is there any reason why dunfell would be stuck at node 12 even though it’s unsupported by node?
Join openembedded-devel@lists.openembedded.org to automatically receive all group messages.