Bug 700236

Summary: [abrt] gnucash-2.4.4-2.fc14: Process /usr/bin/gnucash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Scott Doty <scott>
Component: webkitgtkAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dwmw2, fedora, huzaifas, kevin, martin.sourada, mtasaka, notting, rh-bugzilla.20.horas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:dcd535bfc0df9482f420a6c9da80edda09d504e9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-30 13:19:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Scott Doty 2011-04-27 20:46:49 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 34849 bytes
cmdline: gnucash 2010.gnucash
comment: The financial data is from 2010, so there would have been no entries for the current year.  Defaults for the gl report (and subsiquent null output) might be a factor.
component: gnucash
Attached file: coredump, 107032576 bytes
crash_function: WTF::OSAllocator::reserveAndCommit
executable: /usr/bin/gnucash
kernel: 2.6.35.11-83.fc14.x86_64
package: gnucash-2.4.4-2.fc14
rating: 4
reason: Process /usr/bin/gnucash was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303936350
uid: 500

How to reproduce
-----
1. Opened the "reports" menu item
2. selected "general ledger".
3. CRASH.
Comment 1 Scott Doty 2011-04-27 20:46:52 UTC 
Created attachment 495345 [details]
File: backtrace
Comment 2 Bill Nottingham 2011-04-27 22:14:04 UTC 
Assigning to webkitgtk; this is what crashed.
Comment 3 Kevin Fenzi 2011-04-28 00:58:09 UTC 
How much memory do you have there?

Can you get it to crash everytime with this action?
Comment 4 Bill Nottingham 2011-05-26 19:01:01 UTC 
*** Bug 707870 has been marked as a duplicate of this bug. ***
Comment 5 Horas 2011-05-29 19:05:51 UTC 
The crash always occurs.

Rebuilding gnucash with --with-html-engine=gtkhtml is probably currently the easiest workaround.
Comment 6 Kevin Fenzi 2011-05-29 19:55:09 UTC 
If you do 'echo 1 > /proc/sys/vm/overcommit_memory' 
can you no longer get it to happen?
Comment 7 Horas 2011-05-30 07:10:19 UTC 
Nope, no crash after changing the kernel virtual memory accounting mode
Comment 8 Kevin Fenzi 2011-05-30 13:19:54 UTC 
ok, then this is another case of bug 648319 it sounds like. 

There's a fix commited upstream, but it's not in a release. I guess I can pull the patch into our f15 version at least.

*** This bug has been marked as a duplicate of bug 648319 ***