2 Replies Latest reply on Nov 23, 2008 4:13 AM by PeterFDuke


      I notice that after loading PE7, the second most hungry memory user is photoshopserver.exe. It uses about 30 MB.

      According to someone who seems to be an Adobe employee, this should only run when a .PSD file is "served" into Premiere, and should only be loaded when required.

      Wil Renczes, "photoshopserver.exe" #6, 25 Jan 2008 12:53 pm

      I presume we can kill it via Task Manager if we are not importing PSD files and free up a bit of memory to feed the memory leaks.
        • 1. Re: photoshopserver.exe
          Robert J. Johnston Level 3
          As far back as I can remember, photoshopserver.exe always runs when you run Premiere Elements, and is used for importing .PSD files, as you said.

          I've killed the process and PRE still runs, but you won't be able to process Photoshop files, and probably menus might not load since those are Photoshop files. If I recall, you can rename that file and PRE will still start up.

          The handle count doesn't go out of sight like it did a couple years ago when DivX was installed. Now that was a memory leak.

          I've cramed two hours of video, with hundreds of titles, transitions, etc. with only 1 GB of RAM of which 96 MB is shared RAM for video. That's way better than what Premiere Elements had been capable of doing on my machine in prior versions.

          Sometimes when I minimize Premiere Elements and then restore it, the operating system releases memory, which can help.

          I noticed that with PRE 7 the total commit charge will max out at about 1.5 times my RAM. One way to cause loss conciousness is to copy and paste a large number of clips at one time when the system is low on RAM to begin with. But I digress.
          • 2. Re: photoshopserver.exe
            PeterFDuke Level 1
            Yes, I wondered about menu templates being PSD files, but I no longer do my authoring in PE, so "I'm all right Jack".