We have set up a new lab here on campus with 11 machines running CS6 for our art department. Currently those machines are W7 32bit with an I5 processor and 4gb of memory. They are brand new machines with a fresh image and install of CS6.
At random points of the day we have noticed that Photoshop will hang on measuring memory. We have noticed that this occurs any time an SVCHost process is running at more than 200k. We have tried to narrow down what exactly is causing the SVCHost to spike but have been unsuccessful. We have turned off windows update and virus scanning on those machine to no avail.
I was wondering if anyone had run into this issue on W7 before? We are kind of stumped at the moment and our professors are getting frustrated with not being able to have students use Photoshop when they need them too.
Thanks in adavance
We run this in a campus lab so simply turning off or uninstalling the virus scanner is not feasible.
I am not overly familiar with the software. Is there any diagnostics that can run that would show me what exactly the issue is?
Other posts have sugggested it can be mismatched memory, or other processes. Read this thread.
CS6 really likes to run on 64 bit OS with min. of 8 gigs RAM. Need to plug that into budget if you are going to run latest software.
If you let a Photoshop session that appears to be hanging just sit there for a few minutes, does it continue?
I haven't seen any specific errant startup behavior owing to drive disconnects myself, but Photoshop does under some conditions check the drives in the system. I do, for example, sometimes see a delay in the Preferences - Performance dialog until my disk drives spin up, even though I don't have any scratch partitions on those that are spun down.
Another related possibility: Is there a network printer in use in your environment that is sometimes offline?
I have let it sit there for up rougly 15-20 minutes without it ever starting up.
In regards to the printers yes we map printers at log in as well.
At this point we are going to upgrade the memory and see if it helps because I am really out of ideas.
Hello all - resurrecting this thread as it is the most pertinent to my issues.
My CS6 is also hanging on "Measuring memory". I've checked the network drives and devices and everything seems to be running fine... twice last week waited over 20min with no progression, today after 15min it 'wokeup'.
Anything I can do to trouble shoot this more? I'm not sure if there is some kind of log that I can retireve from somewhere?
for my specs:
Win7 Enterprise X64
8 GB ram
any further info would be greatly appreciated.
I wish I could tell you have I have resolved it but I cannot. We are in a bit of a holding pattern here as we are waiting for the end of the semester next week to install the new RAM and upgrade to W7 64bit.
Something, most likely a drive or network volume, on your system is taking a very long time to access.
You'll have to figure out what it is on your system that is taking so long -- probably by removing drives and drivers until the problem goes away.
Thanks Chris, it does seem particular to CS6 as I have just made the jump from CS5 and (CS4 before that) and have never had this issue before. I do have a bunch of network drives that map on login. Our techs tell me all network drives and devices were working during my hang.
I just read in another thread that it maybe some kind of firewall blocking access to an address... http://forums.adobe.com/message/4707421 could this be the issue? we have MS Forefront here at the studio.
oh forgot to mention that when we re-installed nvidia drivers, this 'seemed' to get cs6 running again after a couple of 'hangs' (or what could have eventually been really slow loads)
I just wanted to follow up on this.
We upgraded the memory from 4gb to 16gb and the OS from W7 32bit to W764 bit. The interesting part was that before the computer was put on the network (which rules out mapped drives) or was given AV software the issue with the SVCHost spiking was already there. Windows updates were also turned off.
I still have not been able to indentify what the OS is doing in the background but the good news is that with the bump in memory it no longer causes Photoshop to hang as there is more than enough memory to go around now.