Same thing is happening is you start MySQL with innodb_page_size=16K(default) as well.

2017-11-22 22:45:24 DEBUG    Will start MySQL with --innodb_buffer_pool_size=1G --innodb_log_file_size=1G --innodb_page_size=16K --early-plugin-load=keyring_file.so --keyring_file_data=/home/shahriyar.rzaev/XB_TEST/server_dir/PS211117-percona-server-5.7.19-17-linux-x86_64-debug/mysql-keyring/keyring --log-bin=mysql-bin --log-slave-updates --server-id=3 --gtid-mode=ON --enforce-gtid-consistency --binlog-format=row

2017-11-22 22:48:14 DEBUG    The following backup command will be executed /home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup --defaults-file= --user=root --password=''  --target-dir=/home/shahriyar.rzaev/XB_TEST/backup_dir/ps_5_7_x_2_4/cycle3/full/2017-11-22_22-48-14 --backup --socket=/home/shahriyar.rzaev/XB_TEST/server_dir/PS211117-percona-server-5.7.19-17-linux-x86_64-debug/socket.sock --compress=quicklz --compress-chunk-size=65536 --compress-threads=4 --encrypt=AES256 --encrypt-key=VVTBwgM4UhwkTTV98fhuj+D1zyWoA89K --encrypt-threads=4 --encrypt-chunk-size=65536 --slave-info --no-version-check --core-file --parallel=10 --throttle=40 --keyring-file-data=/home/shahriyar.rzaev/XB_TEST/server_dir/PS211117-percona-server-5.7.19-17-linux-x86_64-debug/mysql-keyring/keyring --stream="xbstream" > /home/shahriyar.rzaev/XB_TEST/backup_dir/ps_5_7_x_2_4/cycle3/full/2017-11-22_22-48-14/full_backup.stream


171122 22:48:17 [05] Compressing, encrypting and streaming ./sysbench_test_db/sbtest3.ibd
2017-11-22 22:48:17 0x7f285ebfe700  InnoDB: Assertion failure in thread 139811365054208 in file os0file.cc line 8594
InnoDB: Failing assertion: dblwr_recover || memcmp(src + 16 + 4, src + (header.m_original_size + 38U) - 8 + 4, 4) == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:48:17 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup(my_print_stacktrace+0x35)[0x17f6fce]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup(handle_fatal_signal+0x2ab)[0x1165f8f]
/usr/lib64/libpthread.so.0(+0xf130)[0x7f28add1a130]
/usr/lib64/libc.so.6(gsignal+0x37)[0x7f28aba195d7]
/usr/lib64/libc.so.6(abort+0x148)[0x7f28aba1acc8]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup[0x100d142]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup(_ZN11Compression11deserializeEbPhS0_m+0x381)[0xf37a5f]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup(_Z23os_file_decompress_pagebPhS_m+0x30)[0xf37ad0]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup(_Z15xb_fil_cur_readP12xb_fil_cur_t+0x4a7)[0xddb447]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup[0xdbafe6]
/home/shahriyar.rzaev/XB_TEST/server_dir/target/percona-xtrabackup-2.4.x-debug/bin/xtrabackup[0xdbbefc]
/usr/lib64/libpthread.so.0(+0x7df5)[0x7f28add12df5]
/usr/lib64/libc.so.6(clone+0x6d)[0x7f28abada1ad]