l

I don't have FCM notifications and never get this problem on Android while @hpk42 and @adbenitez have FCM notifications via microG and this happens. So this is probably related to...

It is also suspicious that in both logs IMAP loop dies after `src/imap/idle.rs:47: Skip IDLE in "INBOX" because we got interrupt.` log. It skips IDLE and then the thread gets...

Another thought I had is that Android uses CFFI call for `dc_accounts_background_fetch` (and other functions as well). This in turn uses `block_on` which runs the future on the current thread,...

And for the case that it is IMAP parser getting stuck, maybe https://github.com/chatmail/core/pull/6924 will help detect it.

When there is a problem, connectivity view displays IO timeout error in the storage section. So current explanation for how the bug happens: 1. Application is in background and is...

Another attempt at fixing this bug: https://github.com/chatmail/core/pull/7010

@adbenitez reproduced the bug with https://github.com/chatmail/core/pull/6924 merged. The whole log looks like this: ``` 07-19 22:43:46.084 19620 19646 🟠 DeltaChat: [accId=2] Read error on stream 192.168.1.20:443 after reading 9118 and...

100% CPU usage and log spamming should be fixed by https://github.com/chatmail/core/pull/7019

Since it attempts to read, it is not a CPU-only loop, e.g. not an infinite loop in IMAP parser. Before https://github.com/sfackler/tokio-io-timeout/commit/f3c0e8c658f179a941f40b021dbf64e144fab419 the loop got stuck in an infinite loop calling...

This is now closed as there is hope that #7022 fixed it, but can be reopened if the problem appears again.