Automattic/node-canvas

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

Open

#2.228 aberto em 7 de abr. de 2023

Ver no GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (9.524 stars) (1.140 forks)batch import
Help wanted

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

Guia do colaborador

Pilha de tecnologia
nodejsjavascript
Domain
backend
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
5
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
over 1 week
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Understanding of Node.js native addonsKnowledge of V8 pointer compression concepts
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
10
Direção de pesquisa
First, reproduce the segfault with both official and unofficial Node.js builds to confirm scope. Then, examine the node canvas native addon source code (likely in src/ directory) for any direct V8 API calls that may be affected by pointer compression. Look for patterns like using Local handles without proper HandleScope or expecting uncompressed pointers. Also check if there are any upstream issues in Node.js or V8 regarding pointer compression compatibility with native addons. Consider building node canvas from source with debug symbols to get a stack trace of the crash location.