After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157500 - Crash during Import of OFX Data
Crash during Import of OFX Data
Status: VERIFIED OBSOLETE
Product: GnuCash
Classification: Other
Component: Import - OFX
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: Benoit Grégoire
Benoit Grégoire
Depends on:
Blocks:
 
 
Reported: 2004-11-06 06:52 UTC by Volker Englisch
Modified: 2018-06-29 20:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Volker Englisch 2004-11-06 06:52:12 UTC
Starting the OFX importer I am getting the following warning messages displayed
on the terminal:

LibOFX INFO: Created OfxDummyContainer to hold unsupported aggregate OFX
(Above message occured on Line 1, Column 1)
LibOFX INFO: Created OfxDummyContainer to hold unsupported aggregate SIGNONMSGSRSV1
(Above message occured on Line 2, Column 2)
LibOFX INFO: Created OfxDummyContainer to hold unsupported aggregate SONRS
(Above message occured on Line 3, Column 3)
LibOFX INFO: Created OfxDummyContainer to hold unsupported aggregate BANKMSGSRSV1
(Above message occured on Line 14, Column 2)
LibOFX INFO: Created OfxDummyContainer to hold unsupported aggregate STMTTRNRS
(Above message occured on Line 15, Column 3)
WRITEME:  ofx_proc_account() Fill in the account type, default name, currency, etc.
Error: ofx_proc_transaction_cb: WRITEME: Gnucash ofx_proc_transaction():Add
PAYEE and ADRESS here once supported by libofx!

Error: ofx_proc_transaction_cb: WRITEME: Gnucash ofx_proc_transaction():Add
PAYEE and ADRESS here once supported by libofx!

Error: ofx_proc_transaction_cb: WRITEME: Gnucash ofx_proc_transaction():Add
PAYEE and ADRESS here once supported by libofx!

...

Error: ofx_proc_transaction_cb: WRITEME: Gnucash ofx_proc_transaction():Add
PAYEE and ADRESS here once supported by libofx!


This, however, does not appear to affect the importing process.  After going
through my line items imported and matching with the entries in the register I
click "OK" to complete the import.  
At this point GnuCash crashed with the following message in a message box:

Application "/usr/bin/guile" (process 11243) has crashed due to a fatal error.
(Segmentation fault).


On the console is this information displayed:

Error: check_open: transaction 0x8f7c3a8 not open for editing
Error: check_open:      Transaction.c:94


I am running GC 1.8.9 on FC2.
Comment 1 Volker Englisch 2004-11-09 05:31:29 UTC
I have repeated the data load with the same end result.  Gnucash crashed.

However, after getting the data from my bank one week at a time - the original
data is one month worth of data - I was able to load the data successfully.
I was hoping I could identify a single transaction causing the crash but
unfortunately I was not able to.
Comment 2 Christian Stimming 2004-12-17 10:41:50 UTC
Could you provide a stack trace (see
http://bugzilla.gnome.org/getting-traces.cgi for more information on how to do
so), and/or potentially provide the file that causes the crash? Also, how large
was your original file (how many transactions)?
Comment 3 Volker Englisch 2004-12-17 15:15:01 UTC
> Also, how large was your original file (how many transactions)

With "original file" are you refering to the gnucash data file or the OFX file?
Neither of these are especially large.  I'm using GC since April 2004 and I have
about 40-50 transactions a month in my checking account which results in about
500 transactions stored in GC for the checking account and maybe 200
transactions between the remaining accounts.

> Could you provide a stack trace

I can try to load the OFX file again with a GC backup file from around that
time.  I'm not sure though, if the backup file I still have is identical to the
file as it was when the import crashed.
Also, I have upgraded from FC2 to FC3 in the meantime but that shouldn't really
matter since I'm still running GC 1.8.9

> or potentially provide the file that causes the crash

I don't see a problem passing on the data file if you think that would help. 
Comment 4 Christian Stimming 2004-12-17 16:22:25 UTC
Sorry, no, I was referring to the OFX file that you referred to as "the original
data is one month worth of data". The gnucash file probably has nothing to do
with the crash -- I suppose. I was just wondering how the full month of OFX
would crash it but a week of OFX wouldn't. 

If you still have the crashing OFX file aroung, you might consider sending it to
Benoit bock@step.polymtl.ca so that he can check the libofx library. However,
he's quite busy, so it might take several weeks until he can check this.

On a different note, there is a new version of libofx out, libofx-0.7.0, and the
latest gnucash-1.8.10 uses that version. If possible, it would be interesting if
you upgrade libofx and gnucash and check your crashing OFX file again. (But I
know that upgrading gnucash might be quite a job, so if you can't do that for
now, that's fine.) Note that gnucash-1.8.9 will *not* work with the new
libofx-0.7.0.
Comment 5 Volker Englisch 2004-12-17 17:07:41 UTC
I had attempted to build GC from source three times during the last year and
every time I had to cancel the attempt because I wasn't able to complete the
install during a single weekend.  Therefore I don't see my upgrading to GC
1.8.10 successfully happening any time soon.

For now I will try to reload the OFX file with its 50+ transactions and hope I
can create the requested stack trace.

> I was just wondering how the full month of OFX would crash it but a week of 
> OFX wouldn't. 

This didn't surprise me too much.  I've read on the list that the processing
time increases drastically when comparing importing of small versus large OFX
data files. 
Comment 6 Volker Englisch 2004-12-29 22:44:13 UTC
I have re-loaded the "crashing" OFX data file several times - once into an empty
Gnucash file and twice into a backed up gnucash file - but it did load without
crash.  Unfortunately, when the load did crash I had a bunch of adjustments to
apply on my transactions and I'm unable to recreate all of those at this time.

If I do experience another crash during the OFX import I will create a stack
trace and file another bug.  
For now, this bug probably should get cancelled because I'm unable to recreate
the crash.
Comment 7 Christian Stimming 2006-01-24 10:09:19 UTC
As the last comment said, this cannot be reproduced, so it will be closed for now.
Comment 8 John Ralls 2018-06-29 20:48:01 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=157500. Please update any external references or bookmarks.