l

Maybe `Config::NotifyAboutWrongPw` can be removed completely? In-memory `login_failed_once` is enough to prevent adding device message if we only try to connect once. If we fail multiple times with a single...

> I made some unrelated changes, which are easy to track in the individual commits, but they pollute the final PR. Would you prefer to split this into a refactor...

If we remove timeout, users will still be able to send unencrypted message. For setup contact protocol (not joining the group), 1:1 chat is created immediately but is blocked for...

> shouldn't a new scan remove the old, blocked process? We have multiple Bob processes now and old processes are not removed if they still have a chance to finish....

We should revert the revert from #6817 after PGP-contacts (#6796). It adds `is_encrypted()` which makes it possible to see that the chat is encrypted, then there is no need to...

There are only DC reactions, so checking if the reaction is from DC or not is not useful. Reactions should not create chats indeed, otherwise you get an empty chat.

We use `\Seen` flag in cleartext, but should not add more cleartext flags, especially if Delta Chat is not going to read it. This `\Answered` flag is part of IMAP4rev1...

bad_alloc means some C++ code failed to allocate memory. `std::bad_alloc` is a C++ exception: https://en.cppreference.com/w/cpp/memory/new/bad_alloc

SQLite is written in C rather than C++, so it is not even an SQLite crash, but some C++ component in Android application failing. But memory is exhausted by SQLite...

Closing as it is apparently not even reproducible anymore and looks like a generic out of memory crash. There have been changes to how we run checkpointing, maybe the issue...