I have a thread on Arstechnica about this. o2 pointed me over here. http://arstechnica.infopop.net/OpenTopic/page?q=Y&a=tpc&s=50009562&f=12009443&m=370096434

0

My understanding is that svchost is a generic process name for NT services that are developed as dlls. You should be able to see an enumeration of the process that will be launched by the svchost in: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Svchost Not being to familiar with the workings of Photoshop, my guess is that Photoshop launches a dynamic link library based service that manages its virtual memory usage. Large swap files will cause svchost to use more memory. This isn't necessarily a bad thing. Look at your Task Manager processes view, ensuring that you have the Virtual Memory field (VM Size) visible (you can turn this on by going to View>>Select Columns). If the majority of svchost memory usage is in VM, then my guess is that it is working as it is supposed to. The one precaution that you will want to take is ensuring that your paging files occupy contiguous disk space. In NT (2000) you can set an initial and a maximum size for your paging file, allowing it to grow as needed. In my opinion, this is generally a bad idea because it allows opportunity for your paging files to become fragmented, which will severely decrease performance. Give yourself as big of a paging file as you need, but set the initial and maximum size to the same amount, reducing the amount of fragmentation. -Mike.

0

I have found this to be true of many of what are primarily MAC apps that have a Windows version and it happens under Win98, W2K, WMe, etc. The biggies are all Adobe products and Macromedia products - these are MAC companies that support Windows. This always comes up with Macromedia Flash. Memory management and usage is totally different on the MAC. If a process runs out of memory on the MAC one can assign more memory to it. Windows, on the other hand, manages that for you and you can't change it. The result is it uses up memory and file space until it crashes - acts just like a memory leak. When working with these Windows versions of MAC apps, the best thing you can do is save, close, and reopen the apps often.

0

Finally, I managed to get this fixed (as far as I can tell). The problem is that Photoshop 5.5 and Win2000 don't behave well together in certain situations. According to someone over in another forum, if you set Photoshop's memory usage to 30% the problem will go away. It has for me, anyways. =) In photoshop: File>Preferences>Memory & Image cache

0