segfault with node v12.19.0
See original GitHub issuerclnodejs segfaults after a few seconds after receiving a subscription. It only happens with node v12.19, works fine in v12.18.4.
To reproduce:
const rclnodejs = require('rclnodejs');
async function main() {
await rclnodejs.init();
const node = rclnodejs.createNode('test');
rclnodejs.spin(node);
node.createSubscription('std_msgs/msg/String', 'test', {}, console.log);
const pub = node.createPublisher('std_msgs/msg/String', 'test');
pub.publish({ data: 'hello' });
}
main();
Output:
$ node test.js
{ data: 'hello' }
Segmentation fault (core dumped)
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
How to Debug Node.js Segmentation Faults - HTTP Toolkit
A segmentation fault occurs when a program attempts to access a memory location ... When Node.js itself has a bug somewhere, and segfaults...
Read more >cv::FileStorage.open() has an error with “Segmentation fault ...
I have programed the node.js plug-in(add-on) code, which called c++/OpenCV's cv::FileStorage to open the XML file.
Read more >node-segfault-handler - Bountysource
Tool for debugging native Node.js modules and getting stack traces when things go wrong. Become a Bounty Hunter You're a Bounty Hunter.
Read more >node-segfault-handler - npm Package Health Analysis - Snyk
The package node-segfault-handler relies on pkg-config to detect if libunwind-dev is installed, if pkg-config is not present on your system node-segfault- ...
Read more >Node.js v19.3.0 Documentation
new assert.CallTracker() #. Added in: v14.2.0, v12.19.0. Creates a new CallTracker object which ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I got that as well, I think it’s unrelated, it seems more like some v8 changes that causes it instead.
Btw, the offending commit that causes v12.19 to fail has been identified and I think they will be backporting the fix in the next release. I’ll go ahead and close this issue.
https://github.com/nodejs/node/issues/35620 It looks like someone else has the same problem (I got the same stack trace).