Automattic/node-canvas

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

Open

#2,228 opened on 2023年4月7日

GitHub で見る
 (0 comments) (1 reaction) (0 assignees)JavaScript (9,524 stars) (1,140 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.