#967 Crash on any transaction

[Anonymous]

Hello, i have MM 1.2.7 it works well, now i try to update to 1.3.0, download latest build (i try beta 1.3 some months ago with same bug), old database from dropbox open correctly, but whet i try to make any transaction, MM crashes. Please see attached logs may be it help fix the problem.

[Anonymous]

I create new database and copy data viq QIF from old, and seems that it works.

[Anonymous]

Today, without changes, MM crashes again with my new database...

[Stefano]

Looking at your reports, I was unable to determine where the problem could be.
Are you able to create a test database that works with 1.2.7. Test it using the latest build of 1.3.0 and see tf the transactions fail.
Also what operating system are you using?

[Anonymous]

I make new clear DB in 1.2.7, create new account and named it Test, make 1 transaction, then open it in 1.3.0, it say that database updated successfully, i make some transactions, close/open MM all works well. WTF, i think, may be crases caused by cyrillic name of accounts in my real DB, i create new account with cyrillic name and bingo-MM crashed. So i attach DB you can see it for bug. It has 2 accounts -Test and cyrillic, but now crashes at both.

[Anonymous]

And my OS is windows 10 x64

[Nikolay]

I can't reproduce this issue!

[Stefano]

The same as Nikolay, I cannot reproduce this issue as well.

[Nikolay]

I just have tested with mmex_v1.3.0-5-gd661518_h64_portable_build390.zip
Result the same. It's working OK.

[Anonymous]

It's very strange, i open this DB again and it works normally when i make transactions, then close it and open again and after some times it crash again... I open my DB with imported data, check that it crashes every time, then delete almost all data for private reasons and try again-it works, but when i open it again and make some new transaction, it crashed again (so it seems happen after some open/close DB), so i attach archive with screenshot and new database, please check

[Stefano]

Having another look at the previous dump files in xml format does not indicate a crash caused by MMEX. I do notice that One Drive DLL's are opened and the crash stack has messages suggesting that the crash may be external, thus having no references.

Where is your database file located. Is it in a Onedrive folder or a private folder on your hard drive?

I have also placed your latest test file in ondrive and have opened and made sussessful changes without crashing. Using Win7 OneDrive build 17.3.6720.1207

[Stefano]

Sorry, Had a closer look at your screen shots, and db files appear to be on hard-drive.

[Nikolay]

I've catched it.
To reproduce:
1) Start mmex;
2) Do not select any accounts in Navigation tree then press [+] icon in the toolbar to add a new transaction
3) Complete the transaction then press the OK button to save it

account is nullptr.

[Nikolay]

Variable "m_account_id" seems depricated
line 1042 of file 'transdialog.cpp' should be:

    Model_Account::Data* account = Model_Account::instance().get(m_trx_data.ACCOUNTID);

[Anonymous]

Is it possible to add this change in the source code in github, so i can download it from appveyor and check?

[Stefano]

Thanks Nikolay for pin pointing the problem.

In a development environment I could see where the problem was using the crash report. It appears that this info is not present in a non development environments.

GitHub has now been updated with the fix.

[Anonymous]

Confirm, for me bug is gone, my first base works well, big thanks! But for me 1.3.0 work slower than 1.2.7 at same base, see some lags in interface when open account and when scroll in it, hope it gone in future builds)

[Anonymous]

Folks, thanks for working on it can u please release a build with fix.

[Anonymous]

You can download it from appveyor

[Anonymous]

Hi!

After upgrading to version 1.3.0 on Linux 64bit, I can't open my existing database and when I try to create a test file, it crashes right away.

Any udeas how I can fix this?
Thanks!
R

[Stefano]

For further info on this issue please refer to: https://github.com/moneymanagerex/moneymanagerex/issues/957

[Stefano]

On your linux system, rename the existing mmexini.db3 file. A new mmexini.db3 file will be generated clearing all previous initialisation parameters. Then see if you can open your database.

Also use one of the test files above as a comparison.

[Stefano]

Initial report fixed therefore closing.
Subsequent issue ongoing: ref https://github.com/moneymanagerex/moneymanagerex/issues/957