Open nathanchase opened 2 months ago
@nathanchase, the latest version of Bun is v1.1.21, but this crash was reported on Bun v1.1.20.
Are you able to reproduce this crash on the latest version of Bun?
bun upgrade
@nathanchase, the latest version of Bun is v1.1.21, but this crash was reported on Bun v1.1.20.
Are you able to reproduce this crash on the latest version of Bun?
bun upgrade
Yes, although the crash is different and looks to be caused by the sharp
module:
ERROR [worker reload] [worker init] 32 | if (loadedModule) { 1:00:26 PM
33 | const [, loadedPackage] = loadedModule.match(/node_modules[\\/]([^\\/]+)[\\/]/);
34 | help.push(- Ensure the version of sharp aligns with the ${loadedPackage} package: "npm ls sharp");
35 | }
36 | }
37 | throw new Error(help.join('\n'));
^
error:
Something went wrong installing the "sharp" module
symbol 'napi_register_module_v1' not found in native module. Is this a Node API (napi) module?
Possible solutions:
- Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
- Install for the current linux-x64 runtime: "npm install --platform=linux --arch=x64 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install
at node_modules/sharp/lib/sharp.js:37:9
at node_modules/sharp/lib/constructor.js:11:1
at node_modules/sharp/lib/index.js:6:7
at #onError (node:worker_threads:192:11)
How can we reproduce the crash?
Relevant log output
No response
Stack Trace (bun.report)
Bun v1.1.20 (
ae19489
) on linux x86_64 [RunAsNodeCommand]Segmentation fault at address 0x0000001A
ld-temp.o:0
:WTF::Unicode::convertReplacingInvalidSequences
??
ld-temp.o:0
:llint_relativePCBase
ld-temp.o:0
:JSC::Interpreter::executeCall
ld-temp.o:0
:JSC::JSModuleEnvironment::getOwnPropertySlot
ld-temp.o:0
:JSC::VM::drainMicrotasks
JSCell.h:218
:Bun::Process_functionMemoryUsage