Summary: | Claws-Mail 64bit crashes when saving a draft | ||
---|---|---|---|
Product: | Claws Mail (Windows) | Reporter: | mergia |
Component: | default | Assignee: | users |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | liste |
Priority: | P3 | ||
Version: | 3.16.0 | ||
Hardware: | PC | ||
OS: | Windows 10 |
Description
mergia
2018-02-01 21:36:22 UTC
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: http://git.claws-mail.org/ ++ ChangeLog 2018-02-28 19:47:03.203159083 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=a73cd56b0852e8e249abe4ae285946f10dc4cf81 Merge: ebbb94b bafb3e4 Author: Colin Leroy <colin@colino.net> Date: Wed Feb 28 19:47:02 2018 +0100 Merge branch 'master' of file:///home/git/claws http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=bafb3e43d73525659b4b391526880f5119e06af2 Author: Andrej Kacian <ticho@claws-mail.org> 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 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. |