fuse-friends / fuse-native

Multithreaded FUSE bindings for Node JS.
203 stars 29 forks source link

"Illegal hardware instruction" #19

Closed marcotollini closed 4 years ago

marcotollini commented 4 years ago

Hello, I am using the example in the README, but I get an error after I enter the mounted path and I ls twice (in the first one everything is ok):

FUSE library version: 2.9.9
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.27
flags=0x003ffffb
max_readahead=0x00020000
null mount
   INIT: 7.19
   flags=0x00000011
   max_readahead=0x00020000
   max_write=0x00020000
   max_background=0
   congestion_threshold=0
   unique: 1, success, outsize: 40
unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 28915
getattr /
   unique: 2, success, outsize: 120
unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 28922
getattr /

#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 0x7fffb9a45270
 1: 0xa96131  [node]
 2: 0x19614f4 V8_Fatal(char const*, ...) [node]
 3: 0xe58879 v8::internal::GlobalBackingStoreRegistry::Register(std::shared_ptr<v8::internal::BackingStore>) [node]
 4: 0xbc5798 v8::ArrayBuffer::GetBackingStore() [node]
 5: 0xa08559 node::Buffer::New(node::Environment*, char*, unsigned long, void (*)(char*, void*), void*) [node]
 6: 0xa089c3 node::Buffer::New(v8::Isolate*, char*, unsigned long, void (*)(char*, void*), void*) [node]
 7: 0x9fdbad napi_create_external_buffer [node]
 8: 0x7fcd588e29e5  [/home/project/fuse-native/build/Release/fuse.node]
 9: 0x1320b69  [node]
10: 0x1332fd0  [node]
11: 0x1321478 uv_run [node]
12: 0xa6aa64 node::NodeMainInstance::Run() [node]
13: 0x9f9571 node::Start(int, char**) [node]
14: 0x7fcd5b12809b __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
15: 0x99279c  [node]
[1]    28899 illegal hardware instruction  node index.js
SandruSebastian commented 4 years ago

Hello @marcotollini, I had the same issue.

Downgrading node version from 14 to 12.16.3 did the trick for me.

mafintosh commented 4 years ago

@SandruSebastian only on 14? can you check if 13 fails also

marcotollini commented 4 years ago

@SandruSebastian Thanks! In my debugging I tried to check for new npm packages and everything, but I forgot I've updated all the programs on my PC, among which there was node...

@mafintosh I can confirm that 13 works too.