Bug 403396 - KMyMoney 5.0.2 crashes on import of OFX file
Summary: KMyMoney 5.0.2 crashes on import of OFX file
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.0.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-19 13:48 UTC by rabinnh
Modified: 2019-02-25 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rabinnh 2019-01-19 13:48:20 UTC
SUMMARY

KMyMoney immediately crashes when importing a downloaded OFX file.  This has worked for years, but there is apparently something that has changed in either the OFX file or my KMyMoney file.

I am running Ubuntu 18.04 and this occurred on 5.0.1.  I then removed that version and downloaded the source, built, and installed 5.0.2 with the exact same result.

Appears similar to 399422 but it isn't fixed.

STEPS TO REPRODUCE
1. Download OFX file
2. Open File|Import|OFX
3. Select file

OBSERVED RESULT
Immediate crash

EXPECTED RESULT
File will be imported successfully as it has for years in the past


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Ubuntu 18.04 running Mate with KMyMoney and dependencies installed from the repo, then KMyMoney 5.0.1 uninstalled and 5.0.2 installed from build. 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Comment 1 Thomas Baumgart 2019-01-19 15:50:38 UTC
Since you built from source, can you please provide a backtrace? This might give a few hints as to where the problem is located. Also, the used version of libOFX would be very helpful here.

#399422 was caused by a problem in WebConnect which is not used here.
Comment 2 rabinnh 2019-01-20 14:31:01 UTC
Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms ()
    at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
370	../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory.
(gdb) bt
#0  0x00007ffff0387c3c in __memmove_avx_unaligned_erms ()
    at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#1  0x00007ffff0cc4e28 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_erase(unsigned long, unsigned long) ()
    at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x00007fffa52e3db3 in  () at /usr/lib/x86_64-linux-gnu/libofx.so.7
Comment 3 rabinnh 2019-01-20 14:32:09 UTC
Quite obviously in libofx7
Comment 4 Jack 2019-01-25 23:26:28 UTC
Is there any chance of compiling libofx with debug info?  That might give a better idea of exactly what is causing the crash.
Comment 5 Thomas Baumgart 2019-01-26 15:14:23 UTC
(In reply to rabinnh from comment #2)

[...]

> #0  0x00007ffff0387c3c in __memmove_avx_unaligned_erms ()
>     at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
> #1  0x00007ffff0cc4e28 in std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> >::_M_erase(unsigned long,
> unsigned long) ()
>     at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> #2  0x00007fffa52e3db3 in  () at /usr/lib/x86_64-linux-gnu/libofx.so.7

This can't be the whole backtrace. There must be more. Where is the rest of it?
Comment 6 Bug Janitor Service 2019-02-10 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2019-02-25 04:33:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!