MCMrARM

MainActivity was leaked as a result of a bug I fixed in https://github.com/MCMrARM/revolution-irc/commit/564a5794058c9d719efabdca668363001243a437. I am unsure if this is the only leak that was there.

Found another leak. Someone decided that it'd be a great idea that SpannableString's constructor would copy NoCopySpans (SpannableStringBuilder's does not copy them though). It ended up copying a TextView.ChangeWatcher span...

I don't think anything else leaks MainActivity so I'll close this for now. If I'll see any other memory leak I'll reopen it.

Unfortunately it looks like there is another memleak (perhaps of the SQLite database handles), as the app uses >150MB again.

No, that is fine.

So, I presume you set the interval to 15 minutes, and then waited the 15 minutes and the client still didn't reconnect? Are you sure you were on WiFi and...

Ok that indeed sounds like a bug, wtf.

Can you please load the logcat while Revo is stuck, then try to send a message and check if it appears in the logcat? If it doesn't, can you please...

Yeah you can try doing that if you aren't filtering by app.

Can you post the stack trace regarding the "Read error"?