Automattic/node-canvas

doesn't work for node.js with pointer-compression

Open

#2,228 opened on Apr 7, 2023

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (1,140 forks)batch import
Help wanted

Repository metrics

Stars
 (9,524 stars)
PR merge metrics
 (Avg merge 34d 18h) (2 merged PRs in 30d)

Description

Issue

Using canvas with pointer compression node.js builds (from unofficial-builds) always leads to a segmentation fault.

Steps to Reproduce

console.log('before');
const Canvas = require('canvas');
console.log('after');

with pointer compression node.js we got:

before
Segmentation fault

It's probably not guranteed for node-canvas to work on any build, especially unofficial ones, yet the problem looks unexpected, because some other binary addons work well with the node version.

Environment

  • node-canvas 2.11.2
  • node js with pointer compression from unofficial-builds 18.12.1, 18.15.0
  • Debian Linux 11

Contributor guide

Research direction
Investigate why pointer compression in Node.js causes segmentation fault in node canvas native addon. Check if alignment issues exist with Cairo or Skia libraries used by canvas.
Tech stack
javascriptnodejsc
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.jsC++Native addon build tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40