Comment 7 for bug 273951

I think I have seen something quite similar to this bug. I made a fresh report as Bug #1548226 which includes some valid symbolic stack traces. Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the circumstances in which it happens are very similar?

If this is thought to be the same bug then perhaps the upstream records should also be amended as I must be using a more recent version of evolution.