Error while Applying logs on last incremental backup

[Priyanka]

Hello Team,
We are still getting same error with MySQL version: 5.7.13 and Percona Xtrabackup: 2.3.4
We have a Master-Slave environment where we are taking Percona backup from Slave with --safe-slave-backup option, while trying to apply log for incremental backup following error appears
--------------------------------------------------------------------------------------
11:03:54 UTC - xtrabackup got signal 11 ;
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
innobackupex(my_print_stacktrace+0x2c)[0xc4e5ec]
innobackupex(handle_fatal_signal+0x262)[0xa548a2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7fae2a8c9330]
innobackupex(_Z32page_cur_search_with_match_bytesPK11buf_block_tPK12dict_index_tPK8dtuple_t15page_cur_mode_tPmS9_S9_S9_P10page_cur_t+0x168)[0x9d18a8]
innobackupex(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x1044)[0x9870c4]
innobackupex(_Z22row_search_index_entryP12dict_index_tPK8dtuple_tmP10btr_pcur_tP5mtr_t+0x11f)[0x85319f]
innobackupex[0xc77d84]
innobackupex[0xc78da8]
innobackupex(_Z14row_purge_stepP9que_thr_t+0x345)[0xc792a5]
innobackupex(_Z15que_run_threadsP9que_thr_t+0x4f2)[0x9b35b2]
innobackupex(srv_worker_thread+0x2f1)[0x7fb8b1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7fae2a8c1184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fae28ee937d]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup

I want to know the possible reasons that I am getting this error

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1393