This past Wednesday I updated KMyMoney 5.1.2 to build 1211 (kmymoney-5.1-1211-windows-msvc2019_64-cl.exe) from build 1143 (kmymoney-5.1-1143-windows-msvc2019_64-cl.exe). The upgrade went well. I was able to open my KMyMoney file and add transactions to it. Unfortunately, today well attempting to import bank and credit card information (OFX import), KMyMoney crashed. I tried the import function several times using different accounts and institutions. In each case KMyMoney would crash. I downloaded and installed the latest build, 1214 (kmymoney-5.1-1214-windows-msvc2019_64-cl.exe), hoping the newer version would solve the problem. It didn't! KMyMoney continues to crash whenever an attempt is made to import bank or credit card details.

Since windows builds had been failing since September 29th, it's not possible for me to identify at what point (build) the import function began to fail.

To get around the problem for now build 1143 has been reinstalled. This version has no problem importing bank and credit card data.

Have any other Windows users experienced this problem? If so, have you found a way to correct it?

Thanks for reporting. Unfortunately, there is no reference between the build numbers you refer to and the respective code state. Can you please provide the information that is shown in the dialog Help/About KMyMoney for both versions (esp. the one that is working) including the string appended to the version number, please? What would also be interesting to know is if this fails only for online downloads, for OFX file imports or for both.

Thanks for following up, ipwizard. Here is the requested information;

ipwizard wrote:...please provide the information that is shown in the dialog Help/About KMyMoney for both version

The build that's working is identified as

Version 5.1.2-0af86e098

The build that doesn't work is identified as

Version 5.1.2-c2865cbce

In reference to

ipwizard wrote:...would also be interesting to know is if this fails only for online downloads, for OFX file imports or for both.

The problem occurs in both cases,

Thanks for the info. Between those two versions, there is only a single change to the KMyMoney OFX code but at the same time, LibOFX itself was updated from 0.9.13 to 0.10.3 as part of the Windows build. Maybe that has an impact. More investigation necessary. Would you be in a position to craft and provide a sample OFX file that shows the crash but does not contain personal information? That would ease the troubleshooting a lot. Best would be, if you can do that on a mostly empty KMyMoney file that you provide also.

ipwizard wrote:... Would you be in a position to craft and provide a sample OFX file that shows the crash but does not contain personal information? That would ease the troubleshooting a lot. Best would be, if you can do that on a mostly empty KMyMoney file that you provide also.

I've prepared kmy and ofx files that may be used for testing.

PM sent with links to files

A little update on the progress so far:

On Linux everything works without a problem using the supplied demo files

I was able to setup a Windows development environment based on craft, compile all the dependencies, build KMyMoney and create an installable package (which basically just duplicates what we have on binary-factory.kde.org, but now I have control over it). With that package installed, I was able to duplicate the crash as well using the supplied demo files.

Next I tried to run ofxdump utility from the libOFX package (which does not get distributed with KMyMoney but I have it here as part of building libOFX). It does provide all output as expected and no errors on my Linux system. On Windows it crashes (also) Oh, and btw, any other OFX file also crashes, so it is not related to the demo file.

That is as far as I got. I can think, that building libOFX on Windows using craft is causing something that leads to the crashes, because that is the only common factor I can spot so far. I have to further investigate this.

Thank you for the update. I appreciate the effort you're taking to resolve this issue.

Today I spent some time to figure out what is going on. I noticed, that some global variable assignments to control libOFX causes these crashes. BTW, it is exactly these instructions which are causing ofxdump to also crash. Since they are not really necessary, I simply removed them for windows based builds. This results in less debug output on the console while OFX is analyzing the file. I still had no luck to import an OFX file on Windows. But that may be caused by my environment. But at least it does not crash anymore

ipwizard wrote:Today I spent some time to figure out what is going on.... ....at least it does not crash anymore

This is encouraging news! Thanks for keeping on top of this problem. I'll wait to download the latest build until tomorrow. I suspect your changes will take until then to filter through. I'll let you know the outcome once the update is installed.

ipwizard wrote:....... I still had no luck to import an OFX file on Windows. But that may be caused by my environment. But at least it does not crash anymore

I've installed the latest available build, Version 5.1.2-9308f3c33. The import function no longer crashes the application however the OFX Plugin is throwing an error - cannot parse file.


FYI: Builds at https://binary-factory.kde.org/job/KMyMoney_Release_win64/ are failing at the first stage, building craft.

rblackwell wrote:

ipwizard wrote:....... I still had no luck to import an OFX file on Windows. But that may be caused by my environment. But at least it does not crash anymore

I've installed the latest available build, Version 5.1.2-9308f3c33. The import function no longer crashes the application however the OFX Plugin is throwing an error - cannot parse file.

So we're on par I have no idea what that is/could be.

rblackwell wrote:FYI: Builds at https://binary-factory.kde.org/job/KMyMoney_Release_win64/ are failing at the first stage, building craft.

Yes, I saw that. All builds are currently failing and more or less craft is always part of the cause. Not much I can do. This craft build system (I have to pay attention to not misspell it as cruft) is a mystery to me.

ipwizard wrote:

rblackwell wrote:

ipwizard wrote:....... I still had no luck to import an OFX file on Windows. But that may be caused by my environment. But at least it does not crash anymore

I've installed the latest available build, Version 5.1.2-9308f3c33. The import function no longer crashes the application however the OFX Plugin is throwing an error - cannot parse file.

So we're on par I have no idea what that is/could be.

Seems we are!

Is there someone else that might be able to determine what the problem is?