crash seen on PS if the port number for starting GR matches the server port

There is a crash seen on PS while starting GR on a misconfigured server. However the steps on upstream just returns a valid error message

The server ports for starting GR must be different from the server ports. In the below configuration below

cat ~/my.cnf

[mysqld]

#Server configuration

server_id=1
gtid_mode=ON
enforce_gtid_consistency=ON
master_info_repository=TABLE
relay_log_info_repository=TABLE
binlog_checksum=NONE
log_slave_updates=ON
log_bin=binlog
binlog_format=ROW

#Group configuration

transaction_write_set_extraction=XXHASH64
loose-group_replication_group_name="127ad422-203d-495b-ad1f-4b8b35dd2f82"
loose-group_replication_start_on_boot=off
loose-group_replication_local_address= "192.168.1.102:21000"
loose-group_replication_group_seeds= "192.168.1.102:33061, 192.168.1.102:33062, 192.168.1.102:33063"
loose-group_replication_bootstrap_group=off
bind-address = "127.0.0.1"
report_host = "192.168.1.102"

In the above cnf file, loose-group_replication_local_address= "192.168.1.102:21000" has port number (21000) where the server is running. This is incorrect and must be 33061.

 server is started: 
./bin/mysqld --defaults-file=~/my1.cnf --datadir=`pwd`/data1 --port=21000 --socket=/tmp/mysql_21000.sock --plugin-dir=/home/mohit/work/build/PS80_dbg/lib/mysql/plugin --lc-messages-dir=./share --early-plugin-load=keyring_file.so --keyring_file_data=./data/mykey1 --log-error --general-log --log-error-verbosity=3 --core-file &

And client is connected:
./bin/mysql --no-defaults -S/tmp/mysql_21000.sock -uroot

mysql> SET GLOBAL group_replication_bootstrap_group=ON;
Query OK, 0 rows affected (0.00 sec)

mysql> START GROUP_REPLICATION;
ERROR 2013 (HY000): Lost connection to MySQL server during query

2019-08-12T07:52:11.177267Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Unable to announce tcp port 21000. Port already in use?'
2019-08-12T07:52:11.177345Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error joining the group while waiting for the network layer to become ready.'
double free or corruption (fasttop)

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=3
max_threads=151
thread_count=6
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67982 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 0x46000
/home/mohit/work/build/PS80_dbg/bin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x55) [0x46f7088]
/home/mohit/work/build/PS80_dbg/bin/mysqld(handle_fatal_signal+0x424) [0x3572b29]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7fedfa73e890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7fedf8b0ae97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141) [0x7fedf8b0c801]
/lib/x86_64-linux-gnu/libc.so.6(+0x89897) [0x7fedf8b55897]
/lib/x86_64-linux-gnu/libc.so.6(+0x9090a) [0x7fedf8b5c90a]
/lib/x86_64-linux-gnu/libc.so.6(+0x19bd7b) [0x7fedf8c67d7b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_thread_freeres+0x32) [0x7fedf8c68652]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7700) [0x7fedfa733700]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fedf8bed88f]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file

On upstream below error message is returned and the server does not crash:

mysql> START GROUP_REPLICATION;
ERROR 3092 (HY000): The server is not configured properly to be an active member of the group. Please see more details on error log.