Display Corruption
I have a problem with the MD display corrupting. Unfortunately I haven't worked out what the trigger is, or even if it's consistent. It will be working fine, but at some point the display will start overwriting bits of the screen with copies of other bits of the screen. I've attached a short video which hopefully demonstrates the effect. Throughout this video I am just moving the mouse, not clicking (except when I change to Transaction Filter or whatever). Once it starts, this is happening across the whole application, not just the Graphs & Reports window - I just used the Graphs window as a reasonably 'clean' demo. No other application does this.
I've been using MD for a couple of years now, and this problem has existed throughout. I just assumed that at some point an update would magically fix it :-). That said, it's annoying rather than disastrous as restarting MD fixes it for a while - I just have to remember Ctrl-Q to quit, as the menus are corrupted!
Current MD version: 2024.2 (5172). Windows 11 Home, 10.0.22631 Build 22631. But bear in mind this has been happening with earlier versions of both MD and Windows.
Thanks for any help.
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 Stuart Beesley ... on 30 Nov, 2024 08:03 PM
Grab help/console. Upload that here.
2 Posted by Pete C. on 30 Nov, 2024 08:14 PM
Uploaded. This is since I've restarted and the issue hasn't yet re-manifested itself. If you need the console after the issue appears, let me know.
3 Posted by Stuart Beesley ... on 30 Nov, 2024 09:02 PM
4 Posted by mhoggie on 30 Nov, 2024 09:36 PM
just a user,
Is this the same PC used through windows 10 11 and multiple MD builds?
Possible keyboard mouse issue.
5 Posted by Pete C. on 30 Nov, 2024 09:48 PM
@Stuart: all extensions are up to date. I'm clicking around various screens to try and get it to go wrong again, but it's not co-operating at the moment!
@mhoggie It's not the same PC in fact - interesting idea though. Come to think of it, I've changed both the keyboard and the mouse within the last year, so it's been happening both before and after all of those things! I should smention that this is the only app affected - although in fairness it's probably the only Java app I use.
6 Posted by Peter Chalmers on 10 Jan, 2025 08:51 PM
Naturally after raising the problem and unsuccessfully trying for weeks to deliberately get it to recur, I eventually stop thinking about it and *then* it happens again! :-(
I've attached a new Console file. Any thoughts would be appreciated.
7 Posted by dwg on 10 Jan, 2025 10:03 PM
Where is this "F" Drive physically located?
8 Posted by Pete C. on 11 Jan, 2025 11:14 AM
It's a second SSD inside the PC (SATA connected)
9 Posted by sth on 11 Jan, 2025 08:07 PM
I notice that you have an Nvidia card with custom drivers listed on the C; drive. As with most Windows issues, have you tried updating those drivers? It really sounds like corrupted video memory which could be drivers or the video card memory itself.
Have you changed video cards since this problem occurred?
(NOT IK support)
10 Posted by Pete C. on 11 Jan, 2025 08:21 PM
Hi @sth, I generally keep the video drivers updated - and they're up to date at the moment (and so must have been up to date when this recurred yesterday). I'm not sure what you mean by 'custom' drivers? I just run the update from the NVidia app.
I haven't changed the video card, but I have changed the PC :-). This did also happen on the previous PC, although I think that was NVidia too
As far as the corrupted video memory goes, this is the only application on which I've seen a problem - would I not see issues on other applications if the video memory was faulty? [reading that back it sounds sarcastic, but it's a genuine question - I've got no idea!!]
11 Posted by sth on 11 Jan, 2025 08:31 PM
By custom drivers, I mean those specifically from Nvidia instead of default installed with Windows itself.
You might only see it with MD since memory issues can be very very tricky. Sometimes memory problems only happen when nearby memory is accessed. Sometimes it depends on the bit pattern. Sometimes it depends on the timing. Memory tests need to be exhaustive and not just reading and writing serial bytes.
The fact that you changed the PC but this is the same video card in all cases may point to a hardware issue. Of course can't be sure but the low level kind of overwriting graphics on the screen points to a fairly low level issue and shouldn't be part of the programming in Java or other high level languages.
I haven't seen this kind of display corruption but I am a Mac user.
(NOT IK Support)
12 Posted by Pete C. on 11 Jan, 2025 08:47 PM
Ok, thanks. Just to be completely clear, the previous PC had a physically different video card (I didn't do any swapping around of components, just bought a new PC!), but I think that card was also an NVidia model so it would presumably have the drivers in common.
Do you know of any good video card testing tools (for Windows of course - probably not, if you're a Mac user I guess :-))?
Support Staff 13 Posted by Maddy on 15 Jan, 2025 05:28 PM
@Peter
Can you try relocating your data file and let us know if the issue persists after doing so?
To achieve this, you should simply navigate to Extensions->Manage Extensions and install the Toolbox.
- Launch the Toolbox - Select the Update function (from within the Toolbox) and navigate to Menu: General Tools->Relocate this dataset back to the default 'internal' location.
Finally restart Moneydance.
Please keep us posted on your progress, Thank you!
--
Maddy, Infinite Kind Support
14 Posted by Pete C. on 15 Jan, 2025 08:49 PM
@Maddy
OK, I've done the relocation. We'll see if it reappears.
Just curious, is there some mechanism in mind for why changing the file location might make a difference? Or is this a process of elimination, by undoing differences from a 'vanilla' installation?
15 Posted by dwg on 15 Jan, 2025 09:01 PM
I asked where the drive was located because if Moneydance's data files are on say a network drive it can be problematic, when it is on a difference drive within the system I think having a problem is remote.
Most support people will generally like to see a vanilla setup when troubleshooting, it removes any possibilities of a change being the cause.
Support Staff 16 Posted by Maddy on 16 Jan, 2025 10:22 AM
@Peter
When you are syncing your data file with other devices, your data file should be stored in the default location to prevent any problems.
For further information about syncing with other devices, please refer to these articles:
"Syncing with Other Computers" here and
"Syncing with the Mobile App" here
Please keep us posted on your progress, Thank you!
--
Maddy, Infinite Kind Support
17 Posted by mhoggie on 16 Jan, 2025 11:14 AM
just a user,
I re-watched your video again and I noticed a page alignment on your screen that is different from the same report view on my screen (win 10 64bit build 5172)
Your screen alignment on the Transaction Report seems to be skewed to the right after the top few lines. The Tag Report I see at the end of the video looks like it does on my screen. What caught my eye was the alignment of the right side of the Transaction Report with the top right corner of the report. The "Include Memo" text at the far right of the "Description" line is not displayed completely and seems to be off screen to the right of the "X" at the top of the display. Almost like MD is having problems dealing with the font or font size. Is everything under your "Appearance" tab in Preferences set to "Default" ?
18 Posted by Pete C. on 17 Jan, 2025 09:04 PM
@mhoggie
I have no memory of changing things, but I have:
Theme: Default
Font: Default
Numeric Font: Default
Printing Font: Arial 12 Arial
Font Size +3
I'm assuming Font Size is something I've changed, because 'Default' is one of the options for it. I don't know about the 'Printing Font' though?
I've set Font Size back to Default and we'll see how things go (even though the default font now looks *tiny*!). [I also have to remember that's two things I've changed now :-)]
19 Posted by Stuart Beesley ... on 17 Jan, 2025 09:40 PM
I think at this point, IK need to offer to dial in and take a look. IMHO.
20 Posted by Pete C. on 17 Jan, 2025 11:08 PM
Problem is, I can't create the problem on demand - I went, what about 6 weeks without seeing it. Hard to diagnose such a thing, I know.
I have to say @mhoggie's font idea seems plausible to me. Having set it back to default, if I go a week or two without issues I'll try changing it back to +3 and see if the problem recurs.
(Hmmm, if that *is* the issue, I wonder if even larger sizes might trigger it more 'reliably'???)
21 Posted by dwg on 17 Jan, 2025 11:14 PM
Many of us adjust the font size, it is pretty common. I have +3 on one of my Linux systems, I am not near any others at the moment to check what I have there, but I am sure they vary due to different screen sizes and resolutions.
Support Staff 22 Posted by Sean Reilly on 18 Jan, 2025 02:07 PM
I've seen this problem a few times over the years when running Moneydance on Windows. Each time it has been related to the video/graphics driver. It could be that the increased font size increases the likelihood of the problem reappearing. It could also be that Moneydance, being more RAM-intensive than the average software, puts pressure on the video graphics memory that @sth mentioned and reveals a problem in hardware.
If it's possible to reproduce I'd be very interested in doing a screen sharing session with you to try and get to the bottom of the problem. However, there's nothing in moneydance's code that accesses the low-level graphics operations that could cause such a problem, so we'll have to find the solution elsewhere. My guess so far is that graphics drivers are the culprit.
Thanks,
Sean
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com
23 Posted by Pete C. on 20 Jan, 2025 10:19 PM
Thanks for everyone's assistance with this, I really appreciate the contributions.
I think it unlikely (although obviously not impossible!) that there could be a hardware problem triggered by Moneydance and not by the graphically intensive games that I play from time to time. Similarly for the NVidia drivers (although I think they're a slightly more plausible culprit).
I suspect the only way we will get to the bottom of it is if I can find a repeatable set of trigger conditions - not only to assist diagnosis, but also to be confident that any fix has in fact worked. Given that I've had this problem for a couple of years-ish without identifying a trigger, I'm not optimistic :-)
I'm obviously happy to try out any more suggestions though?
24 Posted by Pete C. on 28 Mar, 2025 06:59 PM
I have discovered a consistent trigger for this display corruption!! And discovered another possible bug at the same time.
I have an investment account that has been running for a number of years, and so the "Securities Detail" tab for it has a graph showing the changes in share price. If I move the mouse over the graph line towards the right hand end, so that a popup label appears *and* so that the right-hand edge of the label extends outside the main window. Beyond that it seems a bit uncertain. It seems OK for *some* instances where the label extends over the window edge, but move a bit further to the right and the effect is triggered. A couple of attached images hopefully illustrate that - the "Buy" label extends further than the price label, but the price label triggers the effect and the buy label does not
The new bug that I've noticed is that the X-axis labels are not properly aligned with the data points on the graph - at least in the way I interpret them. The X-axis is labelled with years, with faint dotted vertical lines above the tick mark. My first price point is dated in October 1996, but the point on the graph is significantly left of the midway point between 1996 and 1997, so maybe 6 months behind? This tracks all the way up to today, where the graph ends about 80% of the way through 2024
even though the price history is completed weekly up to 28/Mar/2025.
I've attached a couple of images to illustrate.
With any luck this will provide some clues as to the issue(s)? I'm happy to assist with any additional diagnosis.
25 Posted by Pete C. on 12 May, 2025 05:28 PM
Just a bump to see if anyone has managed to replicate this issue now that I've described a trigger?
Thanks
System closed this discussion on 11 Aug, 2025 05:30 PM.