[moneydance] Moneydance (build 606) frozen for several minutes

[Gordon Alley]

Here's a followup on my original post.
Last night, I reconciled the same account for the month of February, which
included only 37 transactions. I expected to experience a delay after I
clicked the Done button in the reconciliation window, but shorter.

I got the delay, alright, but this time it was much LONGER. When I clicked
the Done button, the MD GUI froze as before, and I left the Mac to watch a
TV program before retiring for the night. I watched the show for almost an
hour, and when I came back to the Mac, the freeze was still in progress!
Activity Monitor showed that MD was using  45-60% of the CPU. The rest of
the apps on the Mac were usable, but a little sluggish. So I left the Mac
chugging along and went to bed.

This morning, the reconcile had completed, with MD showing about 12% CPU
usage. But it left MD in a condition that was odd. Normally, after I click
the Done button for a reconciliation, when it completes, the reconciliation
window closes (as it did after the event I reported in the original post).
In this case it was still open, with only the unreconciled transactions
remaining in the lists. Checking the account register, I could see that all
the transactions I'd reconciled had the expected green checkmarks. Being a
little leery of clicking on the Done button again, I clicked the Finish
Later button.

It looks like all the data is fine.

I did a trivial reconciliation of a savings account earlier last night (1
transaction), and it finished without incident.

This is getting curiouser and curiouser. :-)

-Gordon

On Fri, Apr 4, 2008 at 12:13 AM, Gordon Alley <gordon at gordonalley.com>
wrote:

> iMac G4 800, 1GB RAM, OS X 10.5.2 with current patches
> Mondeydance 2008 (build 606)
>
> Tonight I was reconciling a stock broker statement for January. There were
> about 85 transactions in that period. After I achieved a 0 difference, I
> clicked the DONE button in the reconciliation dialog. I expected a short
> delay at that point, but this time it just sat there. I spent several
> minutes, checking to make sure other apps were still responsive (they were,
> though I could tell the system was pretty busy), and running the Activity
> Monitor (Moneydance was shown as NOT RESPONDING with about 89% of the CPU -
> the Floating CPU Window bar was pegged). Also, when the mouse pointer was
> over a MD window, it was displaying the Spinning Beachball of Death.
> I could select different MD windows and bring them to the front, but its
> menus and other controls were unresponsive. I was about to kill MD with
> CMD-OPT-ESC, but decided to leave it up while I composed this message, in
> case I needed to check anything (and I was dreading repeating the whole
> reconciliation process). After I had started typing this report (on a
> MacBook that's located next to the iMac where MD is running), I happened to
> glance back over at the Activity Monitor, and noticed that MD had dropped
> back to 8.4% CPU usage, and, sure enough, it had completed the the
> reconciliation and returned to normal. It had been unresponsive for at least
> 3-4 minutes.
>
> The Mac I'm running on is pretty slow. Yes, Leopard isn't officially
> supported on anything less than an 867 Mhz machine, but that iMac is
> actually running better now than with Tiger - it might have something to do
> with the fact that I ended up doing a clean install, and left out most of
> the 3rd-party extensions and add-on software gizmos I had loaded it up with
> in its earlier incarnations. But I've been running MD on it for many years,
> and I don't think I've ever experienced a freeze like this.
>
> And I can understand where some operation might cause a delay, but it
> shouldn't stop responding to the OS for that long.
>
> Just thought I'd post this report in case anyone else has had a similar
> experience recently.
>
> -Gordon
>


-- 
Gordon B. Alley
http://www.gordonalley.com