Photoshop CC 64 bit memory usage

I have just built a Windows 7 64 bit PC (Windows 7 Professional) with 16Gb of Ram. However the 64 bit version of Photoshop CC only sees 4gb (or there abouts). This is the same as the 32 bit version.

After a deal more of fiddling and scratching various bits of the anatomy, I have reinstalled Photoshop. The 64 bit version now sees just under 16GB, which I would suggest is now correct.

Similar Messages

Win 7 pro 32 bit memory usage

early 2006 macpro 1,1. installed win 7 pro 32bit on separate wd black caviar640gb. win says it can see my 5gb memory installed, but usable is only 1.99gb. how can i get it to use more of my memory? won't win 32 bit use 4gb??
thanks

32 bit Windows OS can only address 3GB RAM nominally. The actual address space that is addressable depends on system architecture but could range from 2 to 3.75 GB. Even theoretically 32 bit system can only address 2^32 addresses. Then remove reserved/shared address space from that limit.
If you want to address 4GB or more RAM you will need the 64 bit version of Windows.
EDIT
The hatter provided the answer as I was typing. Once again I suffer from having to type using the "hunt and peck method". I must learn to type faster
Message was edited by: BobTheFisherman

Photoshop memory usage extremely high

I opened a clean Photoshop, then opened and viewed about 6-8 PSD files (each one no bigger than 200mb) individually, not all at once. Then with all PSDs closed and Photoshop "empty" I began working in other programs and noticed my computer acting really slow at times. I then noticed that Photoshop was using 12gigs of memory sitting there doing nothing? This happens a lot...I'm done with Photoshop, but Photoshop is not done with memory usage. Really annoying having to close Photoshop after every use just to clean out it's memory hold.
I'm using Photoshop CC 2014.

I've tried purging clipboard and even have deleted all the contents of my Win7 %temp% folder... Photoshop still hogs big amounts of memory.
here is more system info if this helps:
Adobe Photoshop Version: 2014.2.0 20140926.r.236 2014/09/26:23:59:59 x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:12, Stepping:3 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3392 MHz
Built-in memory: 16180 MB
Free memory: 7391 MB
Memory available to Photoshop: 14481 MB
Memory used by Photoshop: 70 %
3D Multitone Printing: Disabled.
Windows 2x UI: Disabled.
Highbeam: Enabled.
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1200, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGLGPUs=1
NumCLGPUs=1
glgpu[0].GLVersion="3.0"
glgpu[0].GLMemoryMB=2048
glgpu[0].GLName="Quadro K2000/PCIe/SSE2"
glgpu[0].GLVendor="NVIDIA Corporation"
glgpu[0].GLVendorID=4318
glgpu[0].GLDriverVersion="9.18.13.1166"
glgpu[0].GLRectTextureSize=16384
glgpu[0].GLRenderer="Quadro K2000/PCIe/SSE2"
glgpu[0].GLRendererID=4094
glgpu[0].HasGLNPOTSupport=1
glgpu[0].GLDriver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
glgpu[0].GLDriverDate="20130514000000.000000-000"
glgpu[0].CanCompileProgramGLSL=1
glgpu[0].GLFrameBufferOK=1
glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="1.30 NVIDIA via Cg compiler"
glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[6553 6]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
clgpu[0].CLPlatformVersion="1.1"
clgpu[0].CLDeviceVersion="1.1 CUDA"
clgpu[0].CLMemoryMB=2048
clgpu[0].CLName="Quadro K2000"
clgpu[0].CLVendor="NVIDIA Corporation"
clgpu[0].CLVendorID=4318
clgpu[0].CLDriverVersion="311.66"
clgpu[0].CUDASupported=1
clgpu[0].CUDAVersion="4.2.1"
clgpu[0].CLBandwidth=5.01167e+010
clgpu[0].CLCompute=192.569
License Type: Subscription
Application folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\
Temporary file path: C:\Users\billw\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
Startup, 921.7G, 377.5G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Required\Plug-Ins\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Plug-ins\
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2014/08/12-23:42:09   79.557478   79.557478
   adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
   AdbePM.dll   PatchMatch 2014/09/07-21:07:38   79.558079   79.558079
   AdobeLinguistic.dll   Adobe Linguisitc Library   8.0.0
   AdobeOwl.dll   Adobe Owl   5.2.4
   AdobePDFL.dll   PDFL 2014/08/18-15:13:12   79.512424   79.512424
   AdobePIP.dll   Adobe Product Improvement Program   7.2.1.3399
   AdobeXMP.dll   Adobe XMP Core 2014/08/20-09:53:02   79.156797   79.156797
   AdobeXMPFiles.dll   Adobe XMP Files 2014/08/20-09:53:02   79.156797   79.156797
   AdobeXMPScript.dll   Adobe XMP Script 2014/08/20-09:53:02   79.156797   79.156797
   adobe_caps.dll   Adobe CAPS   8,0,0,13
   AGM.dll   AGM 2014/08/12-23:42:09   79.557478   79.557478
   ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31
   amtlib.dll   AMTLib (64 Bit)   8.0.0.122212002 BuildVersion: 8.0; BuildDate: Wed Jul 30 2014 15:59:34)   1.000000
   ARE.dll   ARE 2014/08/12-23:42:09   79.557478   79.557478
   AXE8SharedExpat.dll   AXE8SharedExpat 2013/12/20-21:40:29   79.551013   79.551013
   AXEDOMCore.dll   AXEDOMCore 2013/12/20-21:40:29   79.551013   79.551013
   Bib.dll   BIB 2014/08/12-23:42:09   79.557478   79.557478
   BIBUtils.dll   BIBUtils 2014/08/12-23:42:09   79.557478   79.557478
   boost_date_time.dll   photoshopdva   8.0.0
   boost_signals.dll   photoshopdva   8.0.0
   boost_system.dll   photoshopdva   8.0.0
   boost_threads.dll   photoshopdva   8.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.2.6.32411   2.2.6.32411
   CITThreading.dll   Adobe CITThreading   2.2.6.32411   2.2.6.32411
   CoolType.dll   CoolType 2014/08/12-23:42:09   79.557478   79.557478
   dvaaudiodevice.dll   photoshopdva   8.0.0
   dvacore.dll   photoshopdva   8.0.0
   dvamarshal.dll   photoshopdva   8.0.0
   dvamediatypes.dll   photoshopdva   8.0.0
   dvametadata.dll   photoshopdva   8.0.0
   dvametadataapi.dll   photoshopdva   8.0.0
   dvametadataui.dll   photoshopdva   8.0.0
   dvaplayer.dll   photoshopdva   8.0.0
   dvatransport.dll   photoshopdva   8.0.0
   dvaui.dll   photoshopdva   8.0.0
   dvaunittesting.dll   photoshopdva   8.0.0
   dynamiclink.dll   photoshopdva   8.0.0
   ExtendScript.dll   ExtendScript 2014/01/21-23:58:55   79.551519   79.551519
   icucnv40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090
   icudt40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090
   igestep30.dll   IGES Reader   9.3.0.113
   imslib.dll   IMSLib DLL   7.0.0.154
   JP2KLib.dll   JP2KLib 2014/06/28-00:28:27   79.254012   79.254012
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libiomp5md.dll   Intel(R) OpenMP* Runtime Library   5.0
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   LogSession.dll   LogSession   7.2.1.3399
   mediacoreif.dll   photoshopdva   8.0.0
   MPS.dll   MPS 2014/08/18-23:43:19   79.557676   79.557676
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CC 2014   15.2
   Plugin.dll   Adobe Photoshop CC 2014   15.2
   PlugPlugExternalObject.dll   Adobe(R) CEP PlugPlugExternalObject Standard Dll (64 bit)   5.0.0
   PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   5.2.0.46
   PSArt.dll   Adobe Photoshop CC 2014   15.2
   PSViews.dll   Adobe Photoshop CC 2014   15.2
   SCCore.dll   ScCore 2014/01/21-23:58:55   79.551519   79.551519
   ScriptUIFlex.dll   ScriptUIFlex 2014/01/20-22:42:05   79.550992   79.550992
   svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   8.0.0.14 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   8.0.0.14
   VulcanControl.dll   Vulcan Application Control Library   5.0.0.82
   VulcanMessage5.dll   Vulcan Message Library   5.0.0.82
   WRServices.dll   WRServices Fri Mar 07 2014 15:33:10   Build 0.20204   0.20204
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 15.2 (2014.2.0 x001)
   Accented Edges 15.2
   Adaptive Wide Angle 15.2
   Angled Strokes 15.2
   Average 15.2 (2014.2.0 x001)
   Bas Relief 15.2
   BMP 15.2
   Camera Raw 8.6
   Camera Raw Filter 8.6
   Chalk & Charcoal 15.2
   Charcoal 15.2
   Chrome 15.2
   Cineon 15.2 (2014.2.0 x001)
   Clouds 15.2 (2014.2.0 x001)
   Collada 15.2 (2014.2.0 x001)
   Color Halftone 15.2
   Colored Pencil 15.2
   CompuServe GIF 15.2
   Conté Crayon 15.2
   Craquelure 15.2
   Crop and Straighten Photos 15.2 (2014.2.0 x001)
   Crop and Straighten Photos Filter 15.2
   Crosshatch 15.2
   Crystallize 15.2
   Cutout 15.2
   Dark Strokes 15.2
   De-Interlace 15.2
   Dicom 15.2
   Difference Clouds 15.2 (2014.2.0 x001)
   Diffuse Glow 15.2
   Displace 15.2
   Dry Brush 15.2
   Eazel Acquire 15.2 (2014.2.0 x001)
   Embed Watermark 4.0
   Entropy 15.2 (2014.2.0 x001)
   Export Color Lookup Tables NO VERSION
   Extrude 15.2
   FastCore Routines 15.2 (2014.2.0 x001)
   Fibers 15.2
   Film Grain 15.2
   Filter Gallery 15.2
   Flash 3D 15.2 (2014.2.0 x001)
   Fresco 15.2
   Glass 15.2
   Glowing Edges 15.2
   Google Earth 4 15.2 (2014.2.0 x001)
   Grain 15.2
   Graphic Pen 15.2
   Halftone Pattern 15.2
   HDRMergeUI 15.2
   HSB/HSL 15.2
   IFF Format 15.2
   IGES 15.2 (2014.2.0 x001)
   Ink Outlines 15.2
   JPEG 2000 15.2
   Kurtosis 15.2 (2014.2.0 x001)
   Lens Blur 15.2
   Lens Correction 15.2
   Lens Flare 15.2
   Liquify 15.2
   Matlab Operation 15.2 (2014.2.0 x001)
   Maximum 15.2 (2014.2.0 x001)
   Mean 15.2 (2014.2.0 x001)
   Measurement Core 15.2 (2014.2.0 x001)
   Median 15.2 (2014.2.0 x001)
   Mezzotint 15.2
   Minimum 15.2 (2014.2.0 x001)
   MMXCore Routines 15.2 (2014.2.0 x001)
   Mosaic Tiles 15.2
   Multiprocessor Support 15.2 (2014.2.0 x001)
   Neon Glow 15.2
   Note Paper 15.2
   NTSC Colors 15.2 (2014.2.0 x001)
   Ocean Ripple 15.2
   OpenEXR 15.2
   Paint Daubs 15.2
   Palette Knife 15.2
   Patchwork 15.2
   Paths to Illustrator 15.2
   PCX 15.2 (2014.2.0 x001)
   Photocopy 15.2
   Photoshop 3D Engine 15.2 (2014.2.0 x001)
   Photoshop Touch 14.0
   Picture Package Filter 15.2 (2014.2.0 x001)
   Pinch 15.2
   Pixar 15.2 (2014.2.0 x001)
   Plaster 15.2
   Plastic Wrap 15.2
   PLY 15.2 (2014.2.0 x001)
   PNG 15.2
   Pointillize 15.2
   Polar Coordinates 15.2
   Portable Bit Map 15.2 (2014.2.0 x001)
   Poster Edges 15.2
   PRC 15.2 (2014.2.0 x001)
   Radial Blur 15.2
   Radiance 15.2 (2014.2.0 x001)
   Range 15.2 (2014.2.0 x001)
   Read Watermark 4.0
   Render Color Lookup Grid NO VERSION
   Reticulation 15.2
   Ripple 15.2
   Rough Pastels 15.2
   Save for Web 15.2
   ScriptingSupport 15.2
   Shake Reduction 15.2
   Shear 15.2
   Skewness 15.2 (2014.2.0 x001)
   Smart Blur 15.2
   Smudge Stick 15.2
   Solarize 15.2 (2014.2.0 x001)
   Spatter 15.2
   Spherize 15.2
   Sponge 15.2
   Sprayed Strokes 15.2
   Stained Glass 15.2
   Stamp 15.2
   Standard Deviation 15.2 (2014.2.0 x001)
   STL 15.2 (2014.2.0 x001)
   Sumi-e 15.2
   Summation 15.2 (2014.2.0 x001)
   Targa 15.2
   Texturizer 15.2
   Tiles 15.2
   Torn Edges 15.2
   Twirl 15.2
   U3D 15.2 (2014.2.0 x001)
   Underpainting 15.2
   Vanishing Point 15.2
   Variance 15.2 (2014.2.0 x001)
   Virtual Reality Modeling Language | VRML 15.2 (2014.2.0 x001)
   Water Paper 15.2
   Watercolor 15.2
   Wave 15.2
   Wavefront|OBJ 15.2 (2014.2.0 x001)
   WIA Support 15.2 (2014.2.0 x001)
   Wind 15.2
   Wireless Bitmap 15.2 (2014.2.0 x001)
   ZigZag 15.2
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Libraries
   Adobe Color Themes
Installed TWAIN devices: NONE

What's the recommended setting for "Process memory usage" ("process virtual" in UI) for a 64-bit host on a 64-bit OS?

Hi gurus
In resource based throttling, what's the recommended setting for "Process memory usage" ("process virtual" in the resource based throttling tab of the UI) for a 64-bit host
on a 64-bit Windows OS?
According to MS (http://msdn.microsoft.com/en-us/library/ee308808(v=bts.10).aspx):
"By default, the
Process memory usage throttling threshold is set to 25. If this value is exceeded and the BizTalk process memory usage is more than 300 MB, a throttling condition may occur. On a 32-bit
server, you can increase the Process memory usage value to 50. On a 64-bit server, you can increase this value to 100. This allows for more memory consumption by the BizTalk process before throttling
occurs."
Does this mean that 100 is the recommended setting for a 64-bit host on a 64-bit Windows?
Thanks
Michael Brandt Lassen

Hi Michael,
Recommended setting is the default setting which is 25 .dot.
If your situation is abnormal and you see message delivery throttling state to “4” when the following performance counters are high or if you expect any of you integration
process could have impact on following counters, then you can consider the suggestion by Microsoft. Don’t change the default setting.
High process memory
Process memory usage (MB)
Process memory usage threshold (MB)
You can see these counters under “BizTalk:MessageAgent”
You can gauge these performance counter and its maximum values if have done any regression/performance testing in your test servers. If you have seen these counters having
high values and causing throttling, then you can update the Process memory usage.
Or unexpectedly you’re process high throughput messages in production which is causing these counters to go high and cause throttling, then up can update the Process memory
usage.
The above two cases where I know my expected process usage (by doing performance testing) or suddenly my production server processing has gone high due to unexpected business
hike (or any reasons) which caused throttling, then do changes to default throttling setting.
Just changing the default setting without actual reason could have adverse effect where you end up allocating
more processing capacities but the actual message processing message usage ever is low means you end up investing in underutilised resources.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Perfomance/memory usage issues running LR 3.3 on 32 bit Win XP

I'm using LR 3.x for some time now, at the moment my version is LR 3.3. My machine is set up with a 3.6 GHz core 2 duo cpu, 4 GB of RAM and four samsung spinpoint hdd. LR 3.3 runs on Windows XP SP3 32 bit OS, usable memory is 3,25 GB. At HDD 2 LR is installed, at HDD 3 library is located, at HDD 4 LR cache (20 GB) is located. I use one "big" library with around 20.000 raw images. I use 1:1 preview and deactivated deleting preview.
I noticed that LR is working slow after some time of working on raw images. Tools are lagging, rendering takes very long and sometimes I get the error message that not enough virtual memory is available anymore. Also in task manager I noticed a continuos increase of memory usage, starting around 800 MB, ending up - I can't work anymore - around 3,00 GB. Memory usage never lowers.
Do you have any information how to solve this perfomance/memory issues? Thanks and best regards from Germany.

There is a large thread for this.
Here is the link: http://forums.adobe.com/thread/760245?tstart=0
WW

Extensive (very very very extensive) memory usage of host application with CS extension

Hi!
I tried this only under Photoshop CS5 and InDesign CS5 under Windows 7.
When you open and close CS extension panel, the memory taken by Photoshop (InDesign) increases by 6-30MB!
In case of the simple HelloPhotoshop (HelloInDesign) panel from the examples, compiled in release mode, when you open it and close, - it's about 6-10MB each time you do it. And in case of a more complex panel, which uses AIR, etc. it's about 30MB per one panel close/open.
When I use some panels in 5-10 minutes Photoshop (InDesign) increases its memory pool from 600MB up to 1,2 GB. And more. And this memory is never freed, only until Photoshop (InDesign) shutdown.
I tried freeing all my arrays, killing display objects, etc. - nothing helped. Even a simple HelloPhotoshop (HelloInDesign) that does nothing eats memory.
By the way, InDesign eats memory a lot faster .

James, thank you for the very fast answer! I did various tests on the weekend on my computer and computer of my friend.
And I can say, that Debug flag doesn't affect memory consumption. They still eat memory. My steps to reproduce are as follows:
(Windows 7 32 bit)
Photoshop CS5:
1) set HKEY_CURRENT_USER\Software\Adobe\CSXS2Preferences\PlayerDebugMode to 0
2*) check HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\CSXS2Preferences (just in case)
3) Compile HelloPhotoshop example to ZXP and install via Extension manager
4) restart computer
5) Run Photoshop CS5 - Memory consumption: 100 096 KB
6) Open HelloPhotoshop and close it 10 times
7) Memory consumption: 155 840 - 5,574 MB per one close/open
Maybe a garbage collector is expected to run and free this memory, but it never happened in my case. The memory pool was increasing to 1 GB when I was working with one of my panels - with no documents open in Photoshop
In InDesign I tried the same thing with HelloInDesign ( I had to close the panel completely and then open with Window | Extensions | HelloInDesign)
Memory consumption on start: 118 516
Memory consumption after 10 open/close cycles: 197 516
It's 7,9 MB per one close/open
It's the simpliest panel test. When I'm using AIR libraries the memory usage is increasing a lot faster.

High disk usage/high memory usage.

i keep getting high memory usage and high disk usage in ps cs6.
its slow when i open a file. how can i solve this problem.
thank you.
philip.

Not to put too fine a point on it, but more than what? More RAM is almost always better, but you haven't answered most of the questions posed here. The answer might be different if you have 2 GB of RAM or 32 GB of RAM already. A 9 megapixel document could get rather large with a lot of layers, but again you've neglected to give any hard info about its size.
Regarding your video card, that's a bit of a judgment call you need to make. For Photoshop CS6 I currently advise people to try to get a video card that gets a score of 1000 or better on this benchmark: http://www.videocardbenchmark.net/high_end_gpus.html
Video card speed will matter when you're editing those 3D components and video card VRAM will also matter, but possibly even more importantly your GeForce 320 is a bit old, and nVidia may just not be doing their best driver work for it any more.
Everything in general will run more smoothly with a powerful modern video card. I like to recommend a VisionTek ATI Radeon HD 7750 - or if the computer power supply and your budget allow, the even more powerful 7850. VisionTek does a very good job with their hardware, IMO, and it comes with a lifetime guarantee.
Keep in mind that if you switch from nVidia to ATI or vice versa, you should carefully sweep your system to ensure all files from the old card are removed, then visit the web site of the new card's maker and download/install their latest display driver release.
Best of luck.
-Noel

Photoshop CS4 64 bit - Clone Tool does not work (and other tools)

Hello.
I have been using Photoshop for many years going back to v5. I had used Design Prem Suite CS4 for the past year on an XP machine. All worked fine. I recently moved to WIndows 7 (64 bit) to get the add memory usage. CS4 installs both 64 and 32 bit versions on Windows 7 64 bit. So far all good. Any help would be GREATLY APPRECIATED. I am at a dead end and really have no confidence in getting Adobe's help.
My tools are working erratically, especially the cloning and healing tools. I can't even use Photoshop in its current state and this has been going on now for weeks, no help from Adobe on my lates support ticket post.
I canonly say that the clong tools is all over the place including but not limited to:
* When I sample and then click to stamp, lines shoot across across the image as it I clone a line not a single sample area. These stamps can be the length of the enite image.
* when I sample, then click to stamp, some the stamps occurs on some other part of the image.
* when I sample and the click to stamp, nothing happens. I have to click several times.
* when I sample and then click to stampl, the prior location I stamped has the clone applied
There are more, but this is to just give an example.
Notes:
* I have trashed preferences at least 20 times and the problem immediately reappears
* The problem happens in both the 32 bit and 64 bit version of PS running in Windows 7 65 bit
* The problem occurs with OpenGL tuned on and off
* I have installed the latest PC patch 11.0.1
* I have updated my latest NVidia drives. They are current.
* I uninstalled Photoshop (kept the rest of Suite) and that did not work, and the same problem reappeared. I am not uninstalling the complete suite but the reinstall has error (that is a separate issue)
* I have triple monitors running off 2 GeForce 9800 GT cards. These worked flawlessly before upgrading to the Windows 7 64 bit configuration. When I upgrades, I replaced the processor, motherbaord and moved to 12 GB ram. The graphic cards are the same.
Other tool issues:
* I have similar problems with the healing brush
* sometomes the text tool acts strange. I will click to enter text and a large area opens to enter text instead of just the cursor positioned ready for text. Then other times it works normally.
* the move tools sometimesacts strange. For example, if I try to move some test, the text jumps and moves of the image and I have to find it to drag it back on the image.
Thanks in advance

All I can say is... Boy am I glad I have an ATI card that just works (and that's including Photoshop CS4/CS5 32/64 bit)!
One thing I'm not sure was mentioned above... Try changing your Advanced OpenGL preferences to "Basic" or even turning off OpenGL to see if it affects the issue. Also try disabling the Show Overlay function in the CLONE SOURCE palette.
Best of luck getting to the bottom of these problems, guys. If they run on too long, consider switching brands.
-Noel

Lightroom 5.6 would not open. I only get a flash picture then I get an error message. See below message: [Window Title] Adobe Photoshop Lightroom 64-bit [Main Instruction] Adobe Photoshop Lightroom 64-bit does not work more [Content] there was a problem m

Lightroom 5.6 would not open. I only get a flash picture then I get an error message. See below message: [Window Title] Adobe Photoshop Lightroom 64-bit [Main Instruction] Adobe Photoshop Lightroom 64-bit does not work more [Content] there was a problem making the program no longer work properly. The program is closed and there is a notification if a solution is available.

I may have just solved my own problem. Right after posting this I googled bezel lightroom and found this: Flickr: Discussing The word 'bezel' appears in the taskbar. in Adobe Lightroom
I changed the setting in the view menu and now everything appears to be working fine. I cannot explain why it stopped working before because I hadn't made any previous changes to the view options.
Still am curious about the memory usage, though.

Ps CS6 Memory usage 14GB from 50 meg file???

Hey,
Does this memory usage make sense?
I'm working on a 48 meg file, but my RAM usage was up to 13.9 gigs. I just restarted Ps and opened the file and it's up to 10.7 gigs.
Previously I was always maxing out 10 gigs everyday out of 12 available gigs in the machine also working on small files.( 25-30 meg on average) IT tried playing with things forever and finally just tried ordering more RAM. They ended up putting 28 Gigs in the box. And I'm really not seeing any advantage in Photoshop, other than my system still runs OK outside of Ps while I'm working. (Well Rhino 3D still crashes from being out of memory, even though there was still 6 gigs free??? but that's for another forum) Mostly it just freaks me out how much RAM it's using for such a small file...?
I'm just drawing, no filters, not too many layer masks. I do have maybe 15-20 vector smart objects in the file, and I'm at 147 layers. The issue I was having is Pen lag on the Cintiq when I draw starts getting horrible as the RAM usage gets higher. I had been restarting Photoshop constantly to get it to release RAM. But I haven't the last couple days since they doubled the RAM in the machine. And obviously on restart the file still needed a lot of RAM???
Anyone got any sugestions? I can live with the lag, sucks, but I can still work. I just don't understand why these small files are using so much RAM. Back in the day on 32 bit systems with 4gigs of RAM I would sometimes create posters/covers/magazine spreads that were 1.5- even 4 gigs that would have to be saved as Tiff's because PS didn't support a file that big. This machine runs like that everyday. At home I've been doing some freelance book covers that get up to 450 megs now and then and it still runs better, Cintiq at home draws smoother than this machine that costs 3-4 times more!
It's a win 7 64 bit box, 2 Dual core 2.4 Xeons. two quadro 2000's, now 28GB ram, OS on a 560?GB drive with files on a Terrabyte drive that gets backed up. My hardrives arent rated very high, 5.9, but at least im working local to the machine as the network is slow as heck around here!
Thanks for any suggestions anyone might have!

ssttiingya wrote:
The issue I was having is Pen lag on the Cintiq when I draw starts getting horrible as the RAM usage gets higher. I had been restarting Photoshop constantly to get it to release RAM. But I haven't the last couple days since they doubled the RAM in the machine. And obviously on restart the file still needed a lot of RAM???
Anyone got any sugestions? I can live with the lag, sucks, but I can still work.
It's a win 7 64 bit box, 2 Dual core 2.4 Xeons. two quadro 2000's, now 28GB ram, OS on a 560?GB drive with files on a Terrabyte drive that gets backed up. My hardrives arent rated very high, 5.9,
Your issue is stroke lag drawing. You state nothing about the brush and tool being used. Looking at your hardware and knowing Photoshop is using a lot of ram its most likely swapping a lot ram to scratch disk space. Faster disk may help. Also having two quadro 2000 does not improve Photoshop performance over having just one. Yes Photoshop does not give back RAM it allocate during a session even if you close all the open documents. This may well not be a bad thing. Photoshop is surly managing the RAM space it allocates. Having a lot of ram to work with may well cut down on Photoshop RAM swapping and speed thing up.
Your lag problem may not be a ram problem. Some brushes require GPU support and the size of the rush can easily increase lag. For example if I boot my machine and look at RAM used window 7 64bit professional I see 3.5GB allocated 36.5GB free. If I start CS6 open a new document 11"X 14" 300dpi fill it with a spectrum gradient I see 5GB of ram. In use. If I select the mixer brush tool and a large brush size and make quick brush strokes there is quite a bit of lag and my video card is a quadro 4000 a little faster then your quadro 2000. My swap space is on SSD much faster then spinning disk ratting 7.9 out of 7.9.... and I have dual 6 core xeons.
Some brush type tools like blur, smudge, dodge, burn sharpen require a lot of sequential repetitive processing .. a large tip smudge always seems lag on forever... Its the repetitive nature of the processes that cause the latency not so much the compute power.

Premiere crashes when exceeding ~1.2GB memory usage

This is extremely annoying. I have found Premiere to crash when it hits around 1.2GB to 1.5GB of memory usage on medialayer.dll or something. I was able to crash Premiere in just a matter of seconds after launching it and opening my project. I work quickly, so this happens frequently.
Q9450 Yorkfield Quadcore (12MB Cache), clocked at 3.2GHz
4GB of 1200 RAM
All my scratch disks are set to my second partition, which has around or at least 200GB of free space. My page file is set to about 4GB. My machine is defragmented daily by Diskeeper Pro 2008.
I am dealing with 26 video files and have frame thumbnails displaying in the timeline thing (it makes everything all the more easier for what I am specifically doing) and adds up to around a total of 9 to 10 hours of video and audio. I'm chopping out the intro, credits, and midtro from each video, which is basically what I am doing.
However, I am currently downloading the latest update (which is like 50.3MB) that might possibly fix this issue. At least I hope it does. :( This crash/memory leak is going to drive me insane if it cannot be fixed.
EDIT :: I have observed that every time I save, the memory usage goes up by 200KB to 500KB. For each frame thumbnail that Premiere loads, the memory usage goes up by a whopping 2MB+. This will and does quickly add up for the work I'm doing. Photoshop never unloads any of this memory!
EDIT2 :: By the way, the frame thumbnails are 88x65 sized thumbnails.
EDIT3 :: Even with the latest version and update, Premiere Pro CS3 still crashes for the same reason. I haven't seen the memory usage at 1GB though.
EDIT4 :: Latest updates help though, but does not fix the problem. When I minimize Premiere, usage is 17 MB. When I bring it back up, usage is 32MB. I can keep resetting the usage to 17/32MB simply by just minimizing Premiere and bringing it back up again (and the memory usage reset is about instant). So far I've reset it numerous times when reaching levels of around 600MB to 800MB of memory usage and haven't crashed in my current session due to the memory leak yet.
This seems to be only a temporary solution.
http://www.hlrse.net/Qwerty/premiere-memoryleak-workspace.gif
That is my current workspace. I literally keep task manager open with Premiere highlighted like that so that I can watch the memory usage levels (to know when to 'reset' the memory usage) as I work. Right now all I'm doing is zooming in and out, and splitting videos in two (or multiple pieces).

Q9450 Yorkfield (12MB Cache) @ 3.2GHz
2GB G.Skill PC2-6400 (400MHz) x2 (4GB total, running with 3.5GB due to 32-bit limitations)
NVIDIA FX5200 (temporary, waiting for ATI HD4850 to come back from RMA)
500GB Seagate Barracuda 7200.1 SATA-II w/ SATA-II enabled
I have my 500GB harddrive partitioned into two partitions: 40GB (C) and 425GB (D). C is for Windows XP (includes drivers, codecs, and things that relate heavily to the core of Windows; stuff that isn't important enough to backup). D is for everything else, which includes games, utilities/tools, media (images, video, music), developer material, etc.
On D, you would find the following logical layout of folders:
Developer, Games, Media, Network, Utilities, Mozilla Firefox, Temp.
Temp is so that I can (in an organized fashion) set the temporary locations and scratch disks for programs here. All scratch disks are set to D:\Temp\Premiere, and currently reports 121.9GB of free space. I can easily free up 114GB to 240GB of material on D though (which I plan to do sometime anyway).
What information do you want to know? Be specific, I'm not stupid and illiterate like most people.
EDIT :: I didn't mention this in my post, but I did take the precautions to search through the Troubleshooting database for Premiere, and I did read through the optimizations for Windows XP article (which I already had the same suggestions applied to my computer since the dawn of time -- so that wasn't really useful).
EDIT2 :: I checked the troubleshooting link and none of those really apply. (Do you even know what a memory leak is?)
=P

CPU/memory usage of AIR application under Mac 10.4.10

As my AIR application uses a lot of CPU/memory under Mac
(seems better in Windows), I decide to do some basic testing. I
create several applications with different level of complexities.
Below is a table of CPU/memory usage when the application is simply
sitting there. A brief description of the application can be found
in the end of each line.
Here are some results:
[1] Even for an empty application, CPU usage is not zero
(most non-AIR application has 0 CPU usage when doing nothing). Also
the memory usage is huge, comparable to Finder on my computer.
[2] Empty application has 7 threads running.
[3] Indetermined progress bar costs a lot of CPU; and I guess
any other animation costs a lot of CPU too. But if they are
invisible they are fine.
[4] running timer costs CPU.
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE
VSIZE application
10093 adl 1.8% 0:01.85 7 100 292 15.0M 13.8M+ 22.8M 444M
empty
10094 adl 1.9% 0:01.55 7 100 299 15.2M 14.0M+ 23.1M 444M
label
10097 adl 1.9% 0:01.48 7 100 302 15.3M 13.4M 23.7M 445M
progress bar
10095 adl 5.7% 0:02.40 7 100 302 15.4M- 13.2M 23.5M 445M
progress bar (indetermined)
10125 adl 15.9% 0:03.66 7 100 304 15.7M- 13.4M 23.9M 445M 5
progress bar (indetermined)
10126 adl 29.7% 0:10.39 7 100 325 16.7M+ 13.4M+ 24.9M+ 445M
10 progress bar (indetermined)
10128 adl 1.9% 0:01.34 7 100 324 16.1M 13.7M 24.3M 445M 10
progress bar (indetermined), visible=false
10136 adl 1.8% 0:00.76 7 100 323 16.5M+ 13.9M+ 24.7M- 450M
Empty datagrid
10147 adl 1.9% 0:01.60 7 101 328 16.1M 13.8M+ 24.5M- 447M
TabNavigator with two empty VBox children
10138 adl 1.8% 0:01.59 7 100 372 19.4M 13.9M 27.7M 453M
datagrid with 10000 simple rows
10131 adl 3.1% 0:02.38 7 110 348 25.7M 19.3M 34.8M 458M 10
Empty native windows
10143 adl 1.9% 0:00.99 7 100 296 15.1M 13.9M+ 23.2M- 444M
Timer, delay = 100ms, calling an empty function
10145 adl 4.1% 0:02.35 7 100 298 15.0M 14.0M+ 23.2M- 444M
Timer, delay = 100ms, calling function update label position
As to my own application, it's much bigger than these simple
ones. The CPU usually stablizes to 20% and VSIZE is about 1G. There
is no timer running. When I leave the application open for a few
hours, the application will eventually freeze and I have to kill
it.
I am wondering if there are any articles or documents
explaining AIR's CPU/memory usage. And also if AIR is planning to
improve the performance in the next release.

James, thank you for the very fast answer! I did various tests on the weekend on my computer and computer of my friend.
And I can say, that Debug flag doesn't affect memory consumption. They still eat memory. My steps to reproduce are as follows:
(Windows 7 32 bit)
Photoshop CS5:
1) set HKEY_CURRENT_USER\Software\Adobe\CSXS2Preferences\PlayerDebugMode to 0
2*) check HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\CSXS2Preferences (just in case)
3) Compile HelloPhotoshop example to ZXP and install via Extension manager
4) restart computer
5) Run Photoshop CS5 - Memory consumption: 100 096 KB
6) Open HelloPhotoshop and close it 10 times
7) Memory consumption: 155 840 - 5,574 MB per one close/open
Maybe a garbage collector is expected to run and free this memory, but it never happened in my case. The memory pool was increasing to 1 GB when I was working with one of my panels - with no documents open in Photoshop
In InDesign I tried the same thing with HelloInDesign ( I had to close the panel completely and then open with Window | Extensions | HelloInDesign)
Memory consumption on start: 118 516
Memory consumption after 10 open/close cycles: 197 516
It's 7,9 MB per one close/open
It's the simpliest panel test. When I'm using AIR libraries the memory usage is increasing a lot faster.

Indesign CC freezes and maxes out memory usage in Windows 7

I'm having a problem where Indesign will freeze and when I check on it in Task Manager I can see the memory usage climbing until it's using all free memory. I have to kill the task to get it to stop. I have 8GB and it maxed out at 6.5gb this morning. I'm on Windows 7 Pro and am using the 64-bit version of Indesign with the most recent update.

The document I'm working on now is only about 35 pages with 1-3 images per page, nothing too crazy. I don't have any extra plugins from what I recall - how do I check?
I'm using Photoshop and sometimes Illustrator at the same time, but have plenty of free memory until ID goes nuts.

Problem with Firefox and very heavy memory usage

For several releases now, Firefox has been particularly heavy on memory usage. With its most recent version, with a single browser instance and only one tab, Firefox consumes more memory that any other application running on my Windows PC. The memory footprint grows significantly as I open additional tabs, getting to almost 1GB when there are 7 or 8 tabs open. This is as true with no extensions or pluggins, and with the usual set, (firebug, fire cookie, fireshot, XMarks). Right now, with 2 tabs, the memory is at 217,128K and climbing, CPU is between 0.2 and 1.5%.
I have read dozens of threads providing "helpful" suggestions, and tried any that seem reasonable. But like most others who experience Firebug's memory problems, none address the issue.
Firefox is an excellent tool for web developers, and I rely on it heavily, but have now resorted to using Chrome as the default and only open Firefox when I must, in order to test or debug a page.
Is there no hope of resolving this problem? So far, from responses to other similar threads, the response has been to deny any responsibility and blame extensions and/or pluggins. This is not helpful and not accurate. Will Firefox accept ownership for this problem and try to address it properly, or must we continue to suffer for your failings?

55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't.

Problem with scanning and memory usage

I'm running PS CS3 on Vista Home Premium, 1.86Ghz Intel core 2 processor, and 4GB RAM.
I realise Vista only sees 3.3GB of this RAM, and I know Vista uses about 1GB all the time.
Question:
While running PS, and only PS, with no files open, I have 2GB of RAM, why will PS not let me scan a file that it says will take up 300Mb?
200Mb is about the limit that it will let me scan, but even then, the actual end product ends up being less than 100Mb. (around 70mb in most cases)I'm using a Dell AIO A920, latest drivers etc, and PS is set to use all avaliable RAM.
Not only will it not let me scan, once a file I've opened has used up "x" amount of RAM, even if I then close that file, "x" amount of RAM will STILL be unavaliable. This means if I scan something, I have to save it, close PS, then open it again before I can scan anything else.
Surely this isn't normal. Or am I being stupid and missing something obvious?
I've also monitored the memory usage during scanning using task manager and various other things, it hardly goes up at all, then shoots up to 70-80% once the 70ishMb file is loaded. Something is up because if that were true, I'd actually only have 1Gb of RAM, and running Vista would be nearly impossible.
It's not a Vista thing either as I had this problem when I had XP. In fact it was worse then, I could hardly scan anything, had to be very low resolution.
Thanks in advance for any help

55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't.

Photoshop CC 64 bit memory usage

Similar Messages

Maybe you are looking for