Created attachment 350246 [details]
Logs mentioned in the bug description

I am using Geary with Outlook server configured through IMAP.

Everything worked fine until last week. Now, Geary becomes unresponsive after a few minutes from starting. After waiting some time I see "Geary is not responding" dialog box.

I tried to wait quite long but Geary never becomes responsive again.

I have not updated Geary before unresponsiveness problem started so root cause might be somewhere else. Also, *after* problem started I updated Geary to master version (attached logs are created using master version). It didn't help.

I can reproduce this behaviour, however it does not happen after any specific action. It seems that time is a factor.

I am attaching log files from 2 runs:

geary -d --log-network > geary.log
geary -d --log-network > geary.log.1

head geary.log >> unresponsive.log && tail geary.log >> unresponsive.log
head geary.log.1 >> unresponsive.log.1 && tail geary.log.1 >> unresponsive.log.1

I am not attaching full logs as there is some data I don't want to share.

Notice that geary.log and geary.log.1 files have last line cut in the middle. It seems to me that process became unresponsive in the middle of writing to stdout.

Stacktrace from one run taken after Geary became unresponsive:

sudo gdb --q --n --ex bt --batch --pid 19108 > unresponsive-stacktrace.log

I am attaching also /var/log/apt/history.log

I also noticed that on 21.04.2017 I installed updated libjavascriptcoregtk-4.0-18 library - which is present in the stacktrace. Unfortunately, I don't remember if the problem started on 20.04 or 21.04.