Summary: | Crash adding accounts to report | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | William Haller <bill> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | asoliverez, jan_cecile |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
William Haller
2010-05-17 00:20:17 UTC
Can you give an example of a report or an anon file to test the crash? It might take quite a bit of work to create a sanitized copy. May I suggest as a simple test, creating a ledger entry for a stock that was purchased in 1980. Create a monthly report asset report from that (thus the many, many columns). Then add new stocks that have been purchased via the account report editor. This was when the crash occurred. Changing this same report to yearly columns first before adding the new stocks into the list of rows to include worked ok. It just couldn't handle that many rows in the current iteration of the program. I've previously been able to add rows into that report without it crashing on the previous version. There are around 70 or so rows total, of various liquid assets in the report. I tried setting to daily columns for all categories for all dates, and it took a lot of memory, but it worked. Just to give you an idea of how much it took. This report had about 140 categories and data since 2005. KMyMoney got as much as 2GB of RAM to process it. So, can you save your file as anonymous file and attach it here? Go to Save As, and select the anonymous format. That sanitizes the file. Please. Thank you! I really need an anonymized file to make any progress on this, please. Can you point me to a page that describes your anonymous file process (specifically how is the data made anonymous and still kept useful?) In further testing, I've run the file through your consistency check that succeeds. I've deleted all customized reports. Starting with a standard net worth report by months, I select all dates as the range (Jan 1980 to present). It displays top-level data for all months properly. I save this out and restart kmymoney. The next thing I tried was to select totals. That worked. Selecting All or Groups consistently crashes. There is no memory exhaustion - I had htop running while doing it. However, there is a report from glibc of an error kmymoney: malloc(): smallbin double linked list corrupted: 0x00000000079f95c0. It's been a real busy week with end of school here. I'll try to get some more info about the crash, but I'm uncomfortable with shipping off a copy of the data. Instructions on how to create the anonymized form of the file can be found on http://kmymoney2.sourceforge.net/online-manual/details.formats.anonymous.html . Please feel free to send the file directly to Alvaro w/o attaching it here. During the verification process (when you need to duplicate the problem with the anonymized file) you will see what happened to your personal data. It's an XML file, so you can also use your favorite text editor to take a look. Unless we get an anonymized file, we cannot work on this issue in an efficient way. Right now we cannot reproduce the issue, and we need a test file to make any progress. Sorry. I'm not going to provide a file, anonymous or not. The file is simply too large to try to strip down, checking each time if I've still got the bug, and then checking the resulting file to see if it is sufficiently anonymous. I appreciate your difficulty, but I spent my life working in the embedded controller world where all you got was a CPU running light that went out if something drastic happened. That wasn't very efficient either, and diagnosis via logic analyzers isn't fun either. A back trace isn't ideal, but at least its something, and its all I feel I can provide. This isn't an open source issue - I wouldn't send an anonymous file to Microsoft if I was running their software either. Ok. Report back if you have the same problem with the latest version. *** Bug 257533 has been marked as a duplicate of this bug. *** |