> Dave Peticolas wrote:
>
> > > I have had the exact same problem on two occasions. Never had the proble
> m
> > > unless GNUCASH was running. The first time I waited 30 minutes before
> > > rebooting, the next time I waited a full 10 hours to see how long my syst
> em
> > > would thrash. Finally rebooted. System was totally non-responsive.
> >
> > Did you take a look at gnucash's memory usage?
> > Did you notic if one of the .log files was growing?
>
> I was unable to check memory usage.. the system was unresponsive, I couldn't
> even change to a tty session.
> I have a large multitude of GNUCASH.DAT.*.xac, GNUCASH.DAT.*.log, and
> translog.*.log files. None of which seem excessivly large. I assume they wo
> have been cleaned up if there was a good program exit instead of a power down
In fact, those files are not removed by gnucash. You can safely
delete them.
> These two incidents aside, I really like GNUCASH... I've been using it almost
> everynight since 1.3.1 and had problems twice. But its a big problem.
It's definitely a problem. Do you run Gnucash continously (i.e.,
do you leave it open and switch to the window when you want
to use it) or do you run it, exit, and then run again?
Do you remember if a particular action seemed to precipitate
that behavior? What part of gnucash were you working in at the
time?
thanks,
dave
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
