When I try to write a new message in Claws-Mail (64bit version) under Windows 10, the program crashes each time I write more than about 30 characters. The overall amount of characters in the message does not matter, it must be either the time or the amount of newly added characters.
This only happens as long as spell-check is activated. If I disable spellcheck, the program is stable, and I can write and reply to messages with text of any length.
Steps to Reproduce
Reply to any message with spell-check activated and write more than about 30 characters.
The application crashes without any error messages.
The window stays open till I either close it or send the message.
Disable automatic spell check.
What if you disable automatic draft saving every X characters (on Writing page in main preferences) and leave spell checking enabled? Does it still crash?
I was just able to reproduce this crash once, but not anymore, which is weird.
Disabling auto save also prevents the crash.
Strangely enough, any option only changes the program's stability after I completely reboot the computer / windows. That is, if I start with a stable connection, I can compose messages with both options enabled. However, if I restart the computer while Claws had both options enabled, it will still crash if I try to write a message even if I disable them before actually writing the message.
Changes related to this bug have been committed.
Please check latest Git and update the bug accordingly.
You can also get the patch from:
++ ChangeLog 2018-02-28 19:47:03.203159083 +0100
Merge: ebbb94b bafb3e4
Author: Colin Leroy <firstname.lastname@example.org>
Date: Wed Feb 28 19:47:02 2018 +0100
Merge branch 'master' of file:///home/git/claws
Author: Andrej Kacian <email@example.com>
Date: Wed Feb 28 19:43:43 2018 +0100
Fix a dumb double-free on Windows.
Closes bug 3957: Claws-Mail 64bit crashes when saving a draft
I assume bug 3942 should be closed too ?
I want to test it also on different Windows version before closing (I did not have my laptop with me yesterday), but yes, it's the same bug. Thanks for the reminder.
(In reply to comment #4)
> I assume bug 3942 should be closed too ?
As reporter, you can close bug 3942 yourself by clicking on "mark as duplicate" beneath the message window and entering the number of this bug (3957). That will link your bug report to this one and vice versa.
*** Bug 3942 has been marked as a duplicate of this bug. ***