Yonggang Luo

> Just a side note, NAPI is **not** part of JerryScript, it belongs to IoT.js. Beside that's not the right place to discuss I don't really understand what kind of...

Does https://github.com/jerryscript-project/jerryscript/pull/4829 fixed this?

I suggest move icu out of core by providing a port api.

With the following cmake configure options: ["-DJERRY_LINE_INFO=ON", "-DJERRY_GLOBAL_HEAP_SIZE=102400", "-DJERRY_GC_MARK_LIMIT=8"] The tests are running, but the SplayTree benchmark test can not running, it's too slow: JerryScript ``` PROGRESS Richards RESULT Richards...

> `JERRY_LINE_INFO` JERRY_LINE_INFO affect little, and Splay are toooo slow, this should be a bug.

> Splay is a specific test for GC. It was designed to test the evolutional GC. Since JerryScript uses single mark&sweep model it wouldn't perform well in this test. However...

@rerobika For the record, increased to 1024 have on effect ``` lygstate@DESKTOP-94PU0GB:/mnt/c/work/study/languages/typescript/jerryscript/build/linux$ cmake -GNinja ../.. -DJERRY_LINE_INFO=OFF -DCMAKE_BUILD_TYPE=Release -DJERRY_EXTERNAL_CONTEXT=OFF -DJERRY_SYSTEM_ALLOCATOR=OFF -DJERRY_GLOBAL_HEAP_SIZE=512000 -DJERRY_GC_MARK_LIMIT=1024 -- The C compiler identification is GNU 9.3.0 --...

Now found the cause of splay too slow ``` python tools/build.py ^ --clean ^ --lto=OFF ^ --jerry-debugger=ON ^ --jerry-cmdline=ON ^ --jerry-cmdline-snapshot=ON ^ --jerry-math=ON ^ --jerry-ext=ON ^ --amalgam=ON ^ --snapshot-exec=ON ^...

> As it was said before, the splay test was created specifically to test garbage collection, and thus uses a lot of memory and creates a lot of fragmentation. The...

> I am still curious: [WinError 10054] An existing connection was forcibly closed by the remote host - this is a hint, not an error, why can't we simply ignore...