Bug 3521 - Mbox import from Thunderbird crashes on completion
Summary: Mbox import from Thunderbird crashes on completion
Status: RESOLVED FIXED
Alias: None
Product: Claws Mail (Windows)
Classification: Unclassified
Component: default (show other bugs)
Version: 3.12.0
Hardware: PC Windows 7
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2015-09-20 19:04 UTC by cm
Modified: 2016-05-29 01:34 UTC (History)
0 users

See Also:


Attachments

Description cm 2015-09-20 19:04:40 UTC
After a standard install and setting up for Gmail POP, importing any mbox from a Thunderbird profile causes a crash on completion.
Comment 1 Andrej Kacian 2015-10-18 00:28:41 UTC
Can you provide an example mbox file with which Claws Mail crashes?

Also, does the issue still happen with Claws Mail 3.13.0?
Comment 2 cm 2015-10-18 00:51:52 UTC
(In reply to comment #1)
> Can you provide an example mbox file with which Claws Mail crashes?
> 
> Also, does the issue still happen with Claws Mail 3.13.0?

Importing the same files under 3.13.0 works fine. I noticed a fix relating to double notifications and I wonder if this could have been fixed by that. The crashes occur when the import has completed without error and the notification pops up, always saying "2 new messages" regardless of how many were imported.

I'd have to reinstall Thunderbird and slim down an mbox file to get one small enough to upload. Let me know if you still want it.
Comment 3 Andrej Kacian 2015-10-18 01:15:38 UTC
If you can always crash CM 3.12.0 with that mbox file, but never CM 3.13.0, I do not really need it. :) But we need to make sure that 3.13.0 is really unaffected.
Comment 4 cm 2015-10-20 12:37:49 UTC
Ok. I've tried all the mbox files I have on both versions and the crash occurs every time with 3.12.0 but never with 3.13.0. I suspect it's unrelated to the import function, rather something to do with notification.
Comment 5 Andrej Kacian 2015-10-20 13:13:11 UTC
That's good news. But what if you unload the notification plugin on 3.12.0?
Comment 6 Andrej Kacian 2016-05-29 01:34:38 UTC
No response, looks like the crash is indeed fixed. Feel free to reopen if that is not the case.

Note You need to log in before you can comment on or make changes to this bug.