Keith,

Just wanted you to know that since 4.1b5, I have _not_ had those situations where *OVERLY* excessive memory usage (ie, ~1.5GB upwards) has been seen. The most I've seen after having the machine run for ~18 hours without my disturbing it has been ~475M allocated. The average I am seeing now seems to hover between ~125M-175M.

So, thanks for taking the time to look at the logs and having the patience to figure it out!

DisplayFusion seems to no longer freeze now, but I can't say that I am 100% about this, seeing that the last freeze took weeks before freezing...

Just an FYI, B7 seems to of fixed the issues I reported on the old thread, Thanks!

Bad news It just crashed again....

Mine is crashing every 20 minutes or so I am on Beta 7. Log attached.

Sorry, should have told you, am already on 4.1 b9. I think I may finally have actually 99% certain found the culprit though!

DF seems to crash only when I have Photoshop open. Happens on both CS5 and CS6, even when there are no files or such open. I think Photoshop needs to just sit for a while, for DF to crash.

Kinda hope that might bring you closer to a fix!

Updated to Beta 9 and crashed again. Log attached.

Ok I did that will let you know.

Ok I am still crashing it seems to be RDC Main which is remote control desktop manager allows me to open a bunch of RDP sessions to my servers that is crashing that was the only thing I was running on the secondary monitor at the time. I have other things open on the main one though.

Ok Keith, I think am calling my case related to certain circumstances and unpredictability of computers... The frequency my crash happens at is VERY low, like 1 in a million I suppose... When it happens I'll just live with the fact it crashed. And maybe in the future I'll find out what causes it, but for now, I think it's fair to say it's not reproducible, not even by me And that causes the effort to be higher then the gain, so I don't think it's entirely worth it... You seem to have squeezed a lot of the crashes I had earlier out already. And I think the final parts is because I'm not running an entirely "legal" version of photoshop hehe... Or perhaps due too my own systems weirdness (I build it, so it's gotta be weird! )

Thanks for all your time in this matter though!

Kind regards,
Thierry

Not sure if this is the right thread but I followed the prior thread here.

I've been having these lockups for quite a while and put it off on the new SSD I installed a few months ago (about the same time I got DF Pro)

Symptoms are the same as most mentioned. Hard drive access light goes on and stays on. My system seems to go unresponsive, mouse still moves and will sometimes open windows srtart menu but not close it or respond to clicks. The DF taskbars stop working altogether. If I click on the DF Start Menu the space behind the icon goes black and nothing happens.

Last night I noticed that my Phys mem usage had jumped up about a gb over what I normally see at idle so I pulled up taskmanager and saw it was Displayfusion was using the extra mem and about 4100 handles. Computer locked up (as described) right after I tried to close DF.

I don't have Photoshop or use RDC and for me it seemed that it "might" be related to Acronis running scheduled backups, which is why I initially thought it was the SSD. Right now I've turned off everything but the Taskbars, Windows Logon and Wallpaper to see if that helps.

edit: it does seem that this is related to uptime I have stopped allowing my system to run overnight because of it. Most crashes would happen in the evenings or after 18+ hours.

Three monitor setup. W7 x64 latest updates. DF 4.1.0 (Beta 9)

Hi (Windows 7 Pro 64bit, 2 screens)

I haven't been following recent posts on this forum because I completely uninstalled 4.1 beta 9 about a fortnight ago. This is why:

I'd been having complete freezes necessitating safe mode system restores every 2 or 3 days until 4.1. beta 7 (see my earlier postings). At first it seemed to have solved the freeze problem. However a freeze eventually happened and for safety and because of the tedious procedures needed to clear the freeze, I decided not to allow DF to start at all. But I did not uninstall it. To my astonishment I suffered another freeze a day or two later. I then completely uninstalled DF and have not any trouble since.

My observations and guesses:


I'm probably completely wrong, but you never know. A final point - the freeze has always occurred when I have a large number of windows open and am switching screens with one of them

Yes that is the correct program.

Keith,
Just so you know I have been running RDCMan since its release in 2010 and also DF at the same time. I cannot ever remember it causing DF (which I always run with most recent version) to crash.
Pete

I ran it fine as well on my other machine I got a new desktop and now nothing but crashing.

DF is constantly using 10-15% cpu (quad core i7), even when I'm only using the laptop display. It's using around 130,000k memory; I don't know if the memory use is high for this kind of app or not but the cpu use seems through the roof. I'm on 4.1.0 b9. Before jumping up to the beta the cpu usage was even higher so something since then is helping. Oh, and I saw on one thread a question about Bins. I am using Bins.

Requested file attached.

Hey Keith,

A bit off topic maybe, but is there any way I can "unsubscribe" from this topic? I know it's possible somewhere, but I can't find it anymore ...

My .txt file attached here also

@Keith I was on the most current non-beta. Finding the beta on their forums was next to impossible but after searching here someone had posted a link. I installed the Bins beta v1.0.0.224 and DF cpu use sits at around 50m and is using next to no CPU. The bins beta seems to have resolved all my issues! (DF rawks... the program is so handy I love it!)

Keith: some further info.

In order to provide you with the file you wanted I had to install 4.1. beta 9 briefly. I created a restore point, installed DF, made the .txt file, uninstalled DF, then immediately did a system restore, which made a successful warm restart.

I did not go into safe mode to do the system restore - I thought it would be overkill!

This morning the system came up frozen when I switched on. I did my usual safe mode restore (from an earlier restore point for safety) and all is OK so far.

An obvious difference between an ordinary and a safe mode restore is that the latter is using only 1 screen.

Shutdown when the system is frozen takes about 40 minutes. I don't suppose many people can have seen this screen message:

I see it everytime I shut down while DF is running.

Troubleshooting Text attached.

I changed the setting, closed DF, restarted DF and then rebooted with DF running and it worked! Clean reboot without the explorer error.

@Keith, sorry I'm traveling this week. I'll try it when I get back on Saturday.