Fizarak88631
15 discussion posts
This issue may have started with v9.3 as well, but am unsure. Currently on v9.5 (Beta 1).
Since moving to Windows 10 1809 I've had DisplayFusion use a lot of memory and eventually after a few days to a week I will be unable to use my computer without a full restart (which Windows won't do unless I close multiple apps).
Using the "Force Memory Cleanup" option under troubleshooting doesn't clear it. Currently after about 30 hours it is using over 1GB of memory.
Eventually when I come in the office I get a message that a scrip host has run out of memory (will confirm exact text next time it occurs) and the taskbars on the secondary screens are gone. Typically when checking DisplayFusion is using about 2-3GB of memory. There is plent available, but after this point the system stops responding. Even did a clean install of Windows and this is still happening.
I use it at home as well and have no issues, though I am using Windows 10 1803 there.
I've turned on L1 logging and will attach once it happens again (likely in a couple days). Please let me know if you have any suggestions or if this is already being worked on.
Feb 19, 2019 (modified Feb 19, 2019)
•
#1
Fizarak88631
15 discussion posts
Here is the log info. I had accidentally left the settings window open, so hopefully the logging changes were saved. It seemed it only had a couple hours of logs in it for whatever reason. If it's not good I'll try again.
Was un-able to get a screen shot of the error (couldn't open/save anything) Basically it was an error about the Windows Scrip Host. Said it failed to run due to not having enough memory. DisplayFusion taskbars had stopped and was just under 2000MB memory usage. Still had 50% free memory.
Please let me know what additional info I can get you to assist with this.
• Attachment [protected]: DisplayFusionDebugInfo.zip [384,826 bytes]
Fizarak88631
15 discussion posts
I'll give it a try, though I'm hoping we can find a solution.
Let me know what other info I can gather for you - if I need to capture the logs before it essentially crashes on me or something.
So far it looks pretty stable sitting right around 60-63 MB - will update likely on Monday since it's my work PC, but I'll try and take a look this afternoon as it should be noticeable by then.
Fizarak88631
15 discussion posts
Seems to be it. Left it on over the weekend and it's only using 67-70 MB.
Ok, thanks for testing that! Could you re-enable the taskbars and debug logging, let it run for 10 minutes or so, then attach the debug log here again?
Thanks!
Fizarak88631
15 discussion posts
Here you go. Definately looks more useful than the last one.
• Attachment [protected]: DisplayFusionDebugInfo_2_25_19.zip [164,727 bytes]
Thanks! I've passed these logs over to our developers. We'll be sure to let you know when we're able to get it fixed up, or if we need more info from your system.
Thanks!
Fizarak88631
15 discussion posts
I'll keep checking in. Also I noticed, having paid a bit more attention lately, that it seems to grow the most when the computer is locked and I know there isn't a lock event in the previous log.
Went ahead and attached a new one with a lock event just in case you end up needing it.
• Attachment [protected]: DisplayFusionDebugInfo_2_26_19.zip [401,895 bytes]
Ok, interesting! I'll check out the log and keep you posted on what I find out.
Thanks!
Ok, there are some interesting lines in the log and I've passed it over to our devs. I'll be sure to post an update if we think we've gotten it fixed or need more info, we'll be sure to let you know.
Thanks!
Fizarak88631
15 discussion posts
Just checking in. Any update?
Not yet, sorry. I will keep you posted when we have more news.
Thanks!
Fizarak88631
15 discussion posts
Just checking in again. Really miss having those DF taskbars.
Fizarak88631
15 discussion posts
I went back to v9.1 (had an old download of it still) and haven't had any issues. Not sure if this helps any.
Are other versions available? The "old downloads" link only had some older WinXP compatible version available. I'm pretty sure 9.3 worked, but I didn't have a copy of that one saved.
William Shannon
8 discussion posts
I'm having the same exact issue here too. I tend to leave my computer on and locked when I'm away as I tend to work on and monitor multiple things. After about three days, my extra DisplayFusion taskbars are gone and I appear to have no memory left to open an RDP session or even lock my screen. I'm running the latest build of Windows 10 and DisplayFusion 9.5 beta.
William Shannon
8 discussion posts
Hello Keith, please see the attached log files. When I sat back down at my desk at about 11:30am, I noticed that my extra taskbars were gone. It may have happened earlier as I was away from my desk for about an hour and a half.
THanks,
Bill
• Attachment [protected]: DisplayFusionDebugInfo.zip [412,493 bytes]
Thanks! When the taskbars are missing, if you open the Windows Task Manager and go to the Details tab, is DisplayFusion.exe still listed there? If so, what's the memory usage at?
William Shannon
8 discussion posts
Hello Keith,
When it gets to that point, I can't even open Task Manager, the DisplayFusion Settings,; pretty much anything starts complaining about memory issues. I can't even lock the workstation because it states the security components to lock the computer aren't available.
Bill
Fizarak88631
15 discussion posts
This seems to be fixed in 9.5 beta 2.
@Fizarak88631: That's great to hear, thanks for following up!
@William: Could you try updating to 9.5 Beta 2 and let me know if you still have the memory leak on your system?
William Shannon
8 discussion posts
I just updated to beta 3. I'll see how it goes.
William Shannon
8 discussion posts
Here you go, Keith
• Attachment [protected]: DisplayFusionDebugInfo.zip [235,377 bytes]
@William: How's the memory usage in 9.5 Beta 3?
William Shannon
8 discussion posts
@Keith Seems to be stable thus far.
Excellent, glad to hear it!
William Shannon
8 discussion posts
Everything looks great! Thanks for the help, Keith!
That's great to hear, thanks for following up again!