RecoverPoint: Replication Process Restarts with Memory Assertion Failure

2020/02/26 15:36:52.030 - #2 - 6251/6146 - RemoteLogSender: got event (uniqueId=0, eventTime=1582731412018134), EventID_KBOX_ASSERTION_FAILED(3031), SiteUID(0xxxxxxxxxxxxxxxxx), seDetails=Sender=replication, Topic=MemoryShield, msg=Assertion failed: false Line 285 File MemoryShield.cc PID: 6146 Info: memory limit exceeded, no core 
2020/02/26 15:36:52.132 - #0 - 6165/6146 - MemoryShield: errno=0 Assertion failed: false Line 285 File MemoryShield.cc PID: 6146 Info: memory limit exceeded, no core Prior to crashing we ca see ViperDeduper errors as below in replication logs before the memory crash: 
2020/02/26 13:13:08.115 - #0 - 6418/6146 - ViperDeduper::deacknowledgeIndex: errno=0 bug in acknowledgeIndex: RDE_STATUS_INTERNAL_ERROR 
2020/02/26 13:13:08.115 - #0 - 6418/6146 - Transmitter_AO_IMPL::handleViperAck_i: errno=0 error in deacknowledgeIndex: RDE_STATUS_INTERNAL_ERROR 
2020/02/26 13:13:08.116 - #2 - 6418/6146 - ViperLog: EDRS-WIRE:[WireIndexMemory](2): deleteFromAcknowledgeMap: gap in acknowledgements 
2020/02/26 15:36:50.160 - #0 - 6418/6146 - ViperDeduper::deacknowledgeIndex: errno=0 bug in acknowledgeIndex: RDE_STATUS_INTERNAL_ERROR 
2020/02/26 15:36:50.160 - #0 - 6418/6146 - Transmitter_AO_IMPL::handleViperAck_i: errno=0 error in deacknowledgeIndex: RDE_STATUS_INTERNAL_ERROR 
2020/02/26 15:36:50.766 - #2 - 6418/6146 - ViperLog: EDRS-WIRE:[WireIndexMemory](2): deleteFromAcknowledgeMap: gap in acknowledgements

The transmitter tries to get Deduplication Acknowledgement, the Underneath layer gives the error RDE_STATUS_INTERNAL_ERROR. This error is not handled explicitly.

1. Select Protection > Manage Protection.
2. In the left pane, select a Consistency group.
3. In the right pane, click the Link Policy tab.
   1. In the Select link, set a policy diagram, select the relevant link.
   2. Clear the Enable Deduplication checkbox.
4. Click the Apply button.