Summary: | Crashes on return from hibernation overnight | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Gary <gfkde> |
Component: | database | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | onet.cristian, ralf.habacker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | https://commits.kde.org/kmymoney/a0433f9cb0f4657ff195f3de37a7d4c1f385b444 | Version Fixed In: | 4.8.1,5.0.0 |
Sentry Crash Report: |
Description
Gary
2014-11-26 17:19:36 UTC
To the devs, looking at MyMoneyStorageSql::close it seems that the logoff transaction is created only when QSqlDatabase::isOpen() returns true, so it seems that QSqlDatabase::isOpen() might return true even in case the DB went away, should we catch and ignore transactions in this place? I'd say it should try to restore the database connection if it finds such a case. If unable to do so, then yes, it should quit without trying to enter any transaction. This can easily be reproduced with the following steps: 1. start kmymoney 2. open a mysql database 3. stop mysql server Git commit a0433f9cb0f4657ff195f3de37a7d4c1f385b444 by Ralf Habacker. Committed on 29/06/2017 at 19:58. Pushed by habacker into branch '4.8'. Fix 'Crashes on return from hibernation overnight (edit)'. Enabled mysql reconnect option. FIXED-IN:4.8.1 M +1 -0 kmymoney/mymoney/storage/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/a0433f9cb0f4657ff195f3de37a7d4c1f385b444 |