Unrelated question: I don't see the x86 hook exe file listed below the main exe - do you have both hooks enabled on the Troubleshooting tab?
Nope - I don't use the KB shortcuts (strangely enough, as I am usually a kb junkie) so I disabled that hook too.
Quote:
Jon & John, FYI the same thing's going on here.
I have just installed the W7 Final release so I am about to re-install DF (finally!). I'll leave the KB hooks in place this time Jon and see if that makes a difference....
Nev - I wonder if it is b/c of settings we have or our computer setup....
After doing some reading on this issue, it seems like it really isn't an issue at all. Let me try to explain, and feel free to jump in and correct me if I'm wrong. The "private bytes" column is the actual measure of how much memory a process is using. The "virtual size" column is a measure of how much space is allocated (but not necessarily being used). A process on a 32bit version of Windows can have a virtual size of up to 2GB. In the first post, DisplayFusion is actually using ~50MB or RAM, but for some reason it has told Windows that it might want to use >600MB in the future. This is nothing to be concerned about, as it's not really using that memory. If the "private bytes" column sky-rockets then we have some cause for alarm. I hope this is clear, please let me know if you have any questions, but I'm going to mark this topic as "complete" for now. Here are some additional resources:
