Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial sync failure (Node.js version 14) #445

Closed
randomlogin opened this issue May 6, 2020 · 6 comments
Closed

Initial sync failure (Node.js version 14) #445

randomlogin opened this issue May 6, 2020 · 6 comments

Comments

@randomlogin
Copy link

During initial chain sync I get an error which stops the synchronization. Restarting hsd makes this failing block pass, however the error occurs again, every ~500 blocks.

OS: ubuntu 19.04
node.js: 14.0.0
hsd: 2.1.5

[info] (chain) Block 000000000000000f346f7ba3febd63d3baa8494b8953593ed61862f7f3c785d3 (5890) added to chain (size=3283 txs=11 time=5.713345).
[debug] (chain) Retargetting to: 0000000000000264fe0000000000000000000000000000000000000000000000 (0x1a0264fe).


#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 0x7ffc8e8633e0
 1: 0xa96131  [hsd]
 2: 0x19614f4 V8_Fatal(char const*, ...) [hsd]
 3: 0xe58879 v8::internal::GlobalBackingStoreRegistry::Register(std::shared_ptr<v8::internal::BackingStore>) [hsd]
 4: 0xbc5798 v8::ArrayBuffer::GetBackingStore() [hsd]
 5: 0xa0233f node::Buffer::Data(v8::Local<v8::Value>) [hsd]
 6: 0xaf549f node::StreamBase::WriteBuffer(v8::FunctionCallbackInfo<v8::Value> const&) [hsd]
 7: 0xafadb0 void node::StreamBase::JSMethod<&node::StreamBase::WriteBuffer>(v8::FunctionCallbackInfo<v8::Value> const&) [hsd]
 8: 0xc02b0b  [hsd]
 9: 0xc040b6  [hsd]
10: 0xc04736 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [hsd]
11: 0x13a6339  [hsd]
Illegal instruction (core dumped)

lscpu

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       39 bits physical, 48 bits virtual
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               158
Model name:          Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
Stepping:            9
CPU MHz:             888.009
CPU max MHz:         3500.0000
CPU min MHz:         800.0000
BogoMIPS:            4992.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            6144K
NUMA node0 CPU(s):   0-3
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
@tynes
Copy link
Contributor

tynes commented May 8, 2020

@randomlogin

It looks like this is a problem with Node.js v14 that many projects are experiencing

nodejs/node#32463
nodejs/node#32463 (comment)

@tynes tynes changed the title Initial sync failure Initial sync failure (Node.js version 14) May 8, 2020
@Synesso
Copy link

Synesso commented Jun 17, 2020

Upgrading to node 14.4 fixed this for me.

@pinheadmz
Copy link
Member

I think bcoin-org/bcrypto has been recently updated to work around the issue with node. I'll test it out and maybe we can close this issue.

@pinheadmz
Copy link
Member

@chjj has fixed this in bcrypto, I was told:

"to fix it i basically just stack allocated everything, so i wouldnt need to use any external buffers"

Will wait for confirmation before closing this issue - @randomlogin feel like giving this another try and make sure you get the latest version of bcrypto installed?

@pinheadmz
Copy link
Member

@randomlogin can we close this issue? I'm still using node v12 personally but I think we are cleared for v14 now.

@randomlogin
Copy link
Author

@randomlogin can we close this issue? I'm still using node v12 personally but I think we are cleared for v14 now.

After I faced problems with v14 I moved to the v12. I've tried to test by using v14 after the fix, it was working fine, but it was definitely not an extensive usage.

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants