MD freezes using security history window
This comment was split from the discussion: Frozen
In the Currency/Security History window sometimes MD 2012 (825) is not responding when I enter a value in the Current Price: area for a security and select the New button. With the Activity Monitor app it shows MD not using much CPU time <1% or not responding. I have to Force Quit MD and hope it does happen again. It does!
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Jessica Little on Nov 05, 2012 @ 12:21 PM
Hi John,
If you would be willing, could you send me the contents of your error console? Here's how to get the logs:
1) In Moneydance, click on the Help menu and select the Console Window option. This will open the console messages window.
2) While the Console Window is open, attempt to cause the freeze by editing values. Any error messages should be recorded to the Console.
3) Click the Copy to Clipboard button at the bottom to copy the text in the console.
4) Paste the text from the message window into a text file (preferably saved with a .txt or .rtf extension) and attach that file to your response here.
The debugging logs that this produces should not contain any account information, you should check the logs to be safe. If you do see account information, just replace it with something like ACCOUNT NUMBER HERE and it should be fine.
Jessica Little
Moneydance Support
2 Posted by john.prewitt on Nov 10, 2012 @ 07:24 PM
Jessica,
I don't think this technique will work. Since the Console Messages is another widow of MD then when MD freezes how would one get to the Console Messages window? When MD freezes I can't get to any window. I would suggest that MD write its console messages to a log file instead.
I've noticed others are having problems with MD freezing. It may be associated with autosave being performed every 5 minutes. The size of my data file was about 20Mb before the upgrade to MD 2012. The size of the MD 2012 xxx.md file is 40.5Mb. I assume this library file includes the current data file as well as the backup file. I changed the autosave frequency to 20 minutes and no freeze while preforming new values for a dozen or so bonds. I changed it back to 5 minutes, restarted MD and re-entered new values, no freeze.
John
3 Posted by Jon Hoover on Nov 11, 2012 @ 03:22 PM
Hi John,
When Moneydance crashes it writes the console data to a file called errlog.txt. (More accurately, it is already writing it there but it does not delete it.) Depending on your operating system there are different ways to find this file as it is hidden. If you can't find it let me know and I can provide instructions. If the crash happens again it'd be great to see that file. It's a mysterious bug that we haven't quiet got figured yet.
Thanks.
Sincerely,
Jon Hoover, Moneydance Support
4 Posted by john.prewitt on Nov 11, 2012 @ 04:21 PM
Jon,
I'm using the latest version of Mac X (10.8.2). I've tried finding it using suggestions found on the Internet but I could use your technique. In my case, MD did not crash, it was not using much CPU resources, it just would not respond to clicks by the mouse. I used Activity Monitor to Force Quit MD. Is this errlog.txt file being written as MD runs or is it only generate when MD actually crashes? Is the errlog.txt file reset when MD is launched again?
John
5 Posted by john.prewitt on Nov 11, 2012 @ 04:40 PM
Jon,
I did some further searching and I think I found the errlog.txt file. The one I found is in the ~Library/Containers/com.infinitekind.MoneydanceOSX folder. It mirrors a single session of the Console Messages window. It appears that MD starts it over when the Console Messages window is activated from within MD.
John Prewitt
6 Posted by Jon Hoover on Nov 11, 2012 @ 04:46 PM
John,
That's the one!
Sincerely,
Jon Hoover, Moneydance Support
System closed this discussion on Mar 31, 2015 @ 03:51 PM.