The first time it happened I wasn't quite ready to attribute it to GnuCash
since I had lots of other things running even though I suspected GnuCash
might have caused it.
Now, it just happened again and I'm sure it has something to do with
GnuCash.
I sat down and spent the last two hours researching and trying to prepare
for populating GnuCash with my more recent financial activity. I had
entered information regarding my house loan entailing about 7 transactions
(mostly opening balances plus balance adjustments to bring it current) and
I had just moved to this month's checking account activity. I had entered
7 or 8 transactions when GnuCash started to furiously write to the disk
and the machine crawled to a halt. It felt very much like a fork bomb.
The mouse quickly became unresponsive and XMMS stopped playing music
except for half second bursts every so often. I tried to kill X with
CTRL-ALT-BKSP but it wasn't responding and I tried switching to a TTY but
that wasn't responding either so after a minute or two I hit reset. Now,
all my changes tonight are lost, of course.
Right before the disk activity started I noticed that as I entered each
transaction it took slightly longer then the previous one for GnuCash to
recalculate the account balances on the main screen and return. There
were noticeable delays enough that I became concerned how GnuCash would
handle after a year's worth of activity, and upon recording the next
transaction was when the problem occured.
Is this a known bug? Has anyone else experienced this problem? It didn't
crash in the core-dump sense so I'm not sure how to produce useful
debugging info.
If my data had been corrupted some other way could that be causing this?
Thanks in advance for the help...
Sean
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
