Re: [Geary] Geary Crashes

[Jim Nelson <jim yorba org>]

Hi Marc,

Two things.  First, if you could follow the steps outlined here:

https://wiki.gnome.org/Apps/Geary/ReportingABug

That will give us a stack trace, which is the best way for us to figure this out.  Your best bet is to mail the stack trace to geary yorba org  (Is it okay if I share it with Robert?)

Second, there is a potentially related ticket that goes back quite a ways.  One of Geary's earlier maintainers noticed that Chromium would crash if he opened pages from Geary:

https://bugzilla.gnome.org/show_bug.cgi?id=714341

-- Jim


On Wed, Feb 18, 2015 at 11:49 AM, Marc Thomas <mat mthx org> wrote:

On Wed, Feb 18, 2015 at 11:23 AM, Robert Schroll <rschroll gmail com> wrote:

On Wed, Feb 18, 2015 at 11:50 AM, Marc Thomas <mat mthx org> wrote:

I've noticed several times now some crashes in Geary. I think I may be missing a recreation step beause I haven't been able to reproduce it everytime with these steps, but here's what I've noticed. * Client has been in use for a while (reading emails, sending emails, etc) * Open an email with an image attachment and click on image. This just happened with a jpg, though I think I have seen it happen with png before. The image opens in eog. * When I then go to archive the email using the keyboard shortcut "a", Geary crashes. I reopen Geary and the email I attempted to archive is still there. Archiving it again works this time.

That's wonderfully random. I don't know if it matters, but when you archive the email, is eog still open?

So I just ran 9 tests. This was the process I used.

1.) Open Geary

2.) Create Email in account a

3.) Attach Image (jpg/png)

4.) send email to account b

5.) Open email in account b

6.) Open attachment in eog

7a.) Close eog, switch back to Geary

7b.) Leave eog open, switch back to Geary

8.) Press "a" to archive.

Geary crashed 3 times in those tests. once when I closed eog, twice when I left it open.

I quickly tried to reproduce this myself, but was unable. You said it didn't happen all the time, so I may not have stumbled on the correct sequence to trigger it. If you can run geary from a terminal with the debug flag (-d), you'll get a lot of debug output, including, I hope, info about the crash. If you do that and get a crash, we'd be interested in seeing the last bit of that output. Getting a backtrace of the crash would be even more helpful, if that's something you're able to do (see https://wiki.gnome.org/Apps/Geary/ReportingABug).

Here's the last handful of lines from debug

 [deb] 13:44:41 0.000552 imap-engine-minimal-folder.vala:1044: Gmail:mat mthx org:INBOX do_replay_removed_message: local_count=48 local_position=34

 [deb] 13:44:41 0.000596 imap-engine-minimal-folder.vala:1059: Gmail:mat mthx org:INBOX do_replay_removed_message: detaching from local store Email ID [3364/2780]

 [deb] 13:44:41 0.014261 Gmail:mat mthx org:INBOX do_replay_remove_message: completed, current remote_count=47 (reported_remote_count=47 local_count=47 starting local_count=48 remote_position=34 local_position=34 marked=true)

 [deb] 13:44:43 1.593149 geary-controller.vala:2286: Archiving selected messages

 [deb] 13:44:43 0.017397 app-conversation-monitor.vala:641: 1 messages(s) removed to Gmail:mat mthx org:INBOX, trimming/removing conversations...

Segmentation fault (core dumped)

Appologies for not submitting this bug myself. It doesn't look like issues are tracked on your github repo. My guess is they are tracked on Bugzilla, and I don't have an account there yet.

Yeah, our bugtracker is bugzilla.gnome.org. The github repo is an automatic mirror that Gnome created. But they've disabled issues, which is a shame because I much prefer github's issue tracker to bugzilla. Robert

Also of note, I added all the test emails back into my inbox and one by one opened the email, opened the attachment, either closed eog or left it open, and then archived it. After doing that about 6 or 7 times, I got it to crash again. So it might not have much of a process leading up to it, just simply opening an image attachment and archiving the email.