Automattic/node-canvas

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

Open

#2,228 创建于 2023年4月7日

在 GitHub 查看
 (0 评论) (1 反应) (0 负责人)JavaScript (9,524 star) (1,140 fork)batch import
Help wanted

描述

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

贡献者指南

技术栈
nodejsjavascript
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
5
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of Node.js native addonsKnowledge of V8 pointer compression concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
10
研究方向
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.