| Summary: | Crash when saving database | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | smjensen51 |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | joseph.hallstrom |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
smjensen51
2024-10-06 15:38:59 UTC
Does this still happen with 5.2? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. Created attachment 186345 [details]
New crash information added by DrKonqi
kmymoney (5.1.3) using Qt 5.15.13
KMyMoney crashed 3 times while saving the file. The save was initiaed immediately after importing a 37 line csv file. Two previous imports of smaller csv files worked fine.
-- Backtrace (Reduced):
#4 0x0000705d485cc89c in InstitutionsModel::slotObjectModified(eMyMoney::File::Object, QString const&) () at /lib/x86_64-linux-gnu/libkmm_models.so.5
#5 0x0000705d43912e16 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x0000705d4572b687 in MyMoneyFile::objectModified(eMyMoney::File::Object, QString const&) () at /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
#7 0x0000705d45734300 in MyMoneyFile::commitTransaction() () at /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
#8 0x0000705d4575532d in MyMoneyFileTransaction::commit() () at /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
When you say it crashed 3 times, are these new crashes or the same ones originally reported? As was asked in Comment #2, does this still happen with 5.2.1? If this version is not available for your version of Kubuntu, you can test this with one of the standalone versions: Appimage, Flatpak, or Snap. This is important, because even if we discover an actual bug in 5.1.3, that version is no longer supported, and any fix (if still needed in 5.2) would only appear in 5.1.3 (not yet scheduled.) I'm also curious why the backtrace seems incomplete, but that may simply be due to Dr. Konqui, and I'm not sure the few extra lines would help identify the cause. > and any fix (if still needed in 5.2) would only appear in
> 5.1.3 (not yet scheduled.)
That should possibly read "... would only appear in 5.2.2 (not yet scheduled)"
Oops.... Thanks for catching that. Perhaps I needed more coffee. Comment on attachment 186345 [details]
New crash information added by DrKonqi
I imported the csv file once, KMM crashed. I repeated the process twice more with identical results. Then I reduced the file from 31 lines of data to about 15 and imported the smaller file; it worked. Then I tried importing the remainder, and KMM crashed at the end of the import. The backtrace is from that failure.
Have you been able to try this with 5.2.1? If it is not available for your version of Kubuntu (it often isn't for LTS versions) you can try an Appimage, Flatpak, or Snap version. One more thing to check, is after importing, explicitly run a consistency check, and let us know the results. Comment on attachment 186345 [details]
New crash information added by DrKonqi
There was an inconsistency with a newly created Investment that didn't have an opening price set. I found a record in the csv that referenced this investment that had a date that was older than the create date for the specified investment.
Correcting both issues resolved the problem.
Thanks for checking that. It's still not clear exactly why that caused a crash, but you're back in business, so I'm going to close this as WORKSFORME. Not having a price for a security on or before its opening date is certainly something flagged by the consistency check, but I don't see why it should cause any problems, other than perhaps missing values on reports that use the net worth of investments. (I don't know exactly what happens, but I don't think it should cause a crash, especially on saving the file.) |