Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1006610: gnucash: Crash with std::bad_alloc when trying to create any report
65 views
Skip to first unread message
Maximilian Stein
Feb 28, 2022, 11:40:03 AM2/28/22
to
Package: gnucash
Version: 1:4.8-1
Severity: important
Dear Maintainer,
Since recently, Gnucash crashes with an std::bad_alloc exception
whenever I try to open a report. I am unsure whether this bug is
related to #851783.
This is the valgrind output in the moment I try to open a report:
==56964== Warning: set address range perms: large range [0x59c83000, 0x99c85000) (noaccess)
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
==56964==
==56964== Process terminating with default action of signal 6 (SIGABRT)
==56964== at 0x5F348A1: raise (raise.c:50)
==56964== by 0x5F1E545: abort (abort.c:79)
==56964== by 0x5D70889: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C059: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C0C4: std::terminate() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C358: __cxa_throw (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D73020: std::__throw_bad_alloc() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0xE5A00CB: WTF::FileSystemImpl::pathByAppendingComponent(WTF::String const&, WTF::String const&) (in /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.19.11)
==56964== by 0x9EA7B5E: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9EA7BEA: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9E9289A: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9E1ABA0: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964==
==56964== HEAP SUMMARY:
==56964== in use at exit: 71,053,921 bytes in 773,876 blocks
==56964== total heap usage: 7,066,048 allocs, 6,292,172 frees, 941,857,631 bytes allocated
==56964==
==56964== LEAK SUMMARY:
==56964== definitely lost: 80,109 bytes in 116 blocks
==56964== indirectly lost: 63,377 bytes in 2,639 blocks
==56964== possibly lost: 415,818 bytes in 3,965 blocks
==56964== still reachable: 63,512,529 bytes in 734,429 blocks
==56964== of which reachable via heuristic:
==56964== newarray : 211,048 bytes in 30 blocks
==56964== suppressed: 0 bytes in 0 blocks
==56964== Rerun with --leak-check=full to see details of leaked memory
==56964==
==56964== Use --track-origins=yes to see where uninitialised values come from
==56964== For lists of detected and suppressed errors, rerun with: -s
==56964== ERROR SUMMARY: 20027 errors from 232 contexts (suppressed: 0 from 0)
Is this a known issue? Can I assist somehow in further diagnosis?
Thanks for your help!
Best,
Maximilian
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'oldstable'), (100, 'testing-debug'), (100, 'oldstable-updates'), (100, 'oldstable-debug'), (100, 'unstable'), (100, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnucash depends on:
ii gnucash-common 1:4.8-1
ii guile-2.2 2.2.7+1-6+b1
ii guile-3.0-libs 3.0.7-1+b1
ii libaqbanking44 6.4.3beta-1
ii libboost-filesystem1.74.0 1.74.0-14
ii libboost-locale1.74.0 1.74.0-14
ii libboost-program-options1.74.0 1.74.0-14
ii libboost-regex1.74.0 [libboost-regex1.74.0-icu67] 1.74.0-14
ii libc6 2.33-6
ii libcairo2 1.16.0-5
ii libcrypt-ssleay-perl 0.73.06-1+b4
ii libdate-manip-perl 6.86-1
ii libdbi1 0.9.0-6
ii libfinance-quote-perl 1.51-1
ii libgcc-s1 11.2.0-16
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.4-1
ii libgtk-3-0 3.24.31-1
ii libgwengui-gtk3-79 5.9.0-1
ii libgwenhywfar79 5.9.0-1
ii libhtml-tableextract-perl 2.15-1.1
ii libhtml-tree-perl 5.07-2
ii libicu67 67.1-7
ii libofx7 1:0.10.3-1
ii libpango-1.0-0 1.50.4+ds-1
ii libpangocairo-1.0-0 1.50.4+ds-1
ii libpython3.9 3.9.10-1
ii libsecret-1-0 0.20.4-2
ii libstdc++6 11.2.0-16
ii libwebkit2gtk-4.0-37 2.34.6-1~deb10u1
ii libwww-perl 6.61-1
ii libxml2 2.9.12+dfsg-6
ii perl 5.34.0-3
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages gnucash recommends:
pn gnucash-docs <none>
ii python3-gnucash 1:4.8-1
ii yelp 42~beta-2
Versions of packages gnucash suggests:
ii libdbd-mysql 0.9.0-9
pn libdbd-pgsql <none>
pn libdbd-sqlite3 <none>
-- no debconf information
Version: 1:4.8-1
Severity: important
Dear Maintainer,
Since recently, Gnucash crashes with an std::bad_alloc exception
whenever I try to open a report. I am unsure whether this bug is
related to #851783.
This is the valgrind output in the moment I try to open a report:
==56964== Warning: set address range perms: large range [0x59c83000, 0x99c85000) (noaccess)
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
==56964==
==56964== Process terminating with default action of signal 6 (SIGABRT)
==56964== at 0x5F348A1: raise (raise.c:50)
==56964== by 0x5F1E545: abort (abort.c:79)
==56964== by 0x5D70889: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C059: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C0C4: std::terminate() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D7C358: __cxa_throw (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0x5D73020: std::__throw_bad_alloc() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.29)
==56964== by 0xE5A00CB: WTF::FileSystemImpl::pathByAppendingComponent(WTF::String const&, WTF::String const&) (in /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.19.11)
==56964== by 0x9EA7B5E: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9EA7BEA: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9E9289A: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964== by 0x9E1ABA0: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.55.9)
==56964==
==56964== HEAP SUMMARY:
==56964== in use at exit: 71,053,921 bytes in 773,876 blocks
==56964== total heap usage: 7,066,048 allocs, 6,292,172 frees, 941,857,631 bytes allocated
==56964==
==56964== LEAK SUMMARY:
==56964== definitely lost: 80,109 bytes in 116 blocks
==56964== indirectly lost: 63,377 bytes in 2,639 blocks
==56964== possibly lost: 415,818 bytes in 3,965 blocks
==56964== still reachable: 63,512,529 bytes in 734,429 blocks
==56964== of which reachable via heuristic:
==56964== newarray : 211,048 bytes in 30 blocks
==56964== suppressed: 0 bytes in 0 blocks
==56964== Rerun with --leak-check=full to see details of leaked memory
==56964==
==56964== Use --track-origins=yes to see where uninitialised values come from
==56964== For lists of detected and suppressed errors, rerun with: -s
==56964== ERROR SUMMARY: 20027 errors from 232 contexts (suppressed: 0 from 0)
Is this a known issue? Can I assist somehow in further diagnosis?
Thanks for your help!
Best,
Maximilian
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'oldstable'), (100, 'testing-debug'), (100, 'oldstable-updates'), (100, 'oldstable-debug'), (100, 'unstable'), (100, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnucash depends on:
ii gnucash-common 1:4.8-1
ii guile-2.2 2.2.7+1-6+b1
ii guile-3.0-libs 3.0.7-1+b1
ii libaqbanking44 6.4.3beta-1
ii libboost-filesystem1.74.0 1.74.0-14
ii libboost-locale1.74.0 1.74.0-14
ii libboost-program-options1.74.0 1.74.0-14
ii libboost-regex1.74.0 [libboost-regex1.74.0-icu67] 1.74.0-14
ii libc6 2.33-6
ii libcairo2 1.16.0-5
ii libcrypt-ssleay-perl 0.73.06-1+b4
ii libdate-manip-perl 6.86-1
ii libdbi1 0.9.0-6
ii libfinance-quote-perl 1.51-1
ii libgcc-s1 11.2.0-16
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.4-1
ii libgtk-3-0 3.24.31-1
ii libgwengui-gtk3-79 5.9.0-1
ii libgwenhywfar79 5.9.0-1
ii libhtml-tableextract-perl 2.15-1.1
ii libhtml-tree-perl 5.07-2
ii libicu67 67.1-7
ii libofx7 1:0.10.3-1
ii libpango-1.0-0 1.50.4+ds-1
ii libpangocairo-1.0-0 1.50.4+ds-1
ii libpython3.9 3.9.10-1
ii libsecret-1-0 0.20.4-2
ii libstdc++6 11.2.0-16
ii libwebkit2gtk-4.0-37 2.34.6-1~deb10u1
ii libwww-perl 6.61-1
ii libxml2 2.9.12+dfsg-6
ii perl 5.34.0-3
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages gnucash recommends:
pn gnucash-docs <none>
ii python3-gnucash 1:4.8-1
ii yelp 42~beta-2
Versions of packages gnucash suggests:
ii libdbd-mysql 0.9.0-9
pn libdbd-pgsql <none>
pn libdbd-sqlite3 <none>
-- no debconf information
Yuta Hayashibe
Mar 6, 2022, 10:20:04 AM3/6/22
to
Dear Maximilian,
Hello.
I had the same problem.
I was able to open a report window by replacing
libwebkit2gtk-4.0-37=2.34.6-1~deb10u1 with the previous version
libwebkit2gtk-4.0-37=2.34.5-1.
So, libwebkit2gtk-4.0-37=2.34.6-1~deb10u1 may have a problem.
Best,
Yuta Hayashibe
Hello.
I had the same problem.
I was able to open a report window by replacing
libwebkit2gtk-4.0-37=2.34.6-1~deb10u1 with the previous version
libwebkit2gtk-4.0-37=2.34.5-1.
So, libwebkit2gtk-4.0-37=2.34.6-1~deb10u1 may have a problem.
Best,
Yuta Hayashibe
Yuta Hayashibe
Mar 13, 2022, 3:50:03 AM3/13/22
to
Hello,
With libwebkit2gtk-4.0-37=2.34.6-1~deb11u1, they worked fine.
Yuta Hayashibe
With libwebkit2gtk-4.0-37=2.34.6-1~deb11u1, they worked fine.
Yuta Hayashibe
0 new messages