From 4859485768d8111c90ab44dcf32d43584e868fd1 Mon Sep 17 00:00:00 2001
From: levlam <levlam@telegram.org>
Date: Wed, 10 Apr 2019 13:42:46 +0300
Subject: [PATCH] Do not erase DeleteMessage log event while closing.

GitOrigin-RevId: 588eeb309964f489186c4614d0dca4c820aedf39
---
 td/telegram/MessagesManager.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/td/telegram/MessagesManager.cpp b/td/telegram/MessagesManager.cpp
index 6d5f4060a..4e5bfe26a 100644
--- a/td/telegram/MessagesManager.cpp
+++ b/td/telegram/MessagesManager.cpp
@@ -23018,7 +23018,7 @@ void MessagesManager::do_delete_message_logevent(const DeleteMessageLogEvent &lo
 
     MultiPromiseActorSafe mpas{"DeleteMessageMultiPromiseActor"};
     mpas.add_promise(PromiseCreator::lambda([logevent_id](Result<Unit> result) {
-      if (result.is_error()) {
+      if (result.is_error() || G()->close_flag()) {
         return;
       }
       binlog_erase(G()->td_db()->get_binlog(), logevent_id);