Dear Maintainer,


Since upgrading from Jessie/Stable to Stretch/Testing, Icedove has been
crashing for me across multiple machines.

This sometimes just happens while I'm working on a completely different
virtual-desktop, but often, it happens when I'm switching folders
within icedove, particularly when the folders are quite large.

I'm no expert in debugging, but I followed the instructions on how to
submit a stacktrace, so I can attach two stacktraces from crashes that
happened today. The first was while I was working in a different
window/desktop entirely, and the second happened while I was in the
application switching folders.

Any thoughts appreciated.  Though there were several existing bugreports
regarding crashes, I'm unfortunately not good enough with stacktraces
to determine whether this is a duplicate issue.  This is happening often
though, so if any more information is required, I can get it.

Another segfault trace just now.

Another segfault trace

Another crash almost immediately

Another.

Is there any worth in me continuing to add data to this bug, or has this
just dropped into a blackhole?

Hello Robin,

we see all the bug reports and new logs that are provided to existing
reports. But we are "only" package maintainers and our possibilities to
fix such segfault issues are quite zero. So no, reporting issues isn't
useless.

Specific issues like these are probably better reported upstream but
some user don't want to do this. But we don't have mostly the time to do
the reporting upstream or can't simply reproduce some issues.

The segfaulting of the icedove binary is annoying but we can't solve
this. The reason for the segfaults are probably related a little bit on
the used GCC. Debian testing is using GCC 6.3.0 and Mozilla is still
using 4.8 as far as I remeber.

Regards
Carsten

I am also experiencing random crashes on testing. But I learned that
with v45 this is also happening on stable.