deasync
deasync copied to clipboard
Issues when using in AWS lambda
I tried to use deasync in my node app that runs in AWS lambda. It turned out generating a lot of errors that seem to relate to memory management or something like it. This is one of the errors.
*** Error in `/var/lang/bin/node': corrupted double-linked list: 0x00000063c620d640 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7b8bd)[0x7fd6efde08bd]
/lib64/libc.so.6(+0x7c4fe)[0x7fd6efde14fe]
/var/lang/bin/node(_ZN4node7NodeBIO4FreeEP6bio_st+0x72)[0x63c37137a2]
/var/lang/bin/node(BIO_free_all+0xba)[0x63c2c7580a]
/var/lang/bin/node(SSL_free+0xcf)[0x63c2c26fdf]
/var/lang/bin/node(_ZN4node6crypto7SSLWrapINS_7TLSWrapEE10DestroySSLEv+0x29)[0x63c3710719]
/var/lang/bin/node(_ZN4node7TLSWrap10DestroySSLERKN2v820FunctionCallbackInfoINS1_5ValueEEE+0xc4)[0x63c37175e4]
/var/lang/bin/node(_ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE+0xeb)[0x63c2e23b5b]
/var/lang/bin/node(+0x77d67b)[0x63c2e9367b]
/var/lang/bin/node(+0x77e017)[0x63c2e94017]
[0x46dab7060c7]
After this stack there is a long "Memory map".
Is there something that can be done in order to avoid these errors? Or is it that AWS lambda and deasync are not liking each other?