Photoshop CC memory at 4.5GB
hey folks
i just tarted using Photoshop CC - even without any files open - it was still using 4.5GB of memory! isnt this a "bit" excessive?
i am using Windows 7 Ultimate, with 8GB of RAM.
what can be done?
thanks
How did you get that number? I started my system Windows 7 Pro start task manager and hit print screen then started Photoshop CC created a new document and pasted in the clip. I then popped the task manager on top and did a prtscrn and pasted th the clipboard, can see the memory is use before CC and the memory in use with cc up with one screen size document open.
looks like 600MB to me Task manager process window state Photoshop usinf 480MB something is happening on you system or you have many open documents. Photoshop can use lots of memory that is why I installed 40GB of ECC RAM.
Similar Messages
-
I have a Core 2Duo 8400, intel motherboard DP35DP, 150 Raptor, and 1T seagate 7200rpm 16 mb cache, 8gb memory. Window Vista Home Premiun 64 bit.
I am using this PC exclusively to run Photoshop CS3, I not runnig other application.I have a Partition Hard Drive of 35Gb specially for scratch disk.
My system indicate that I have 8gb ram, but in Photoshop Preference, Performance, only show 3.4gb.
Can you tell me why I have only 3.4gb?Photoshop Ram Memory- Trouble
Miguel Marin - 01:28am Apr 10, 2008 Pacific
I have a Core 2Duo 8400, intel motherboard DP35DP, 150 Raptor, and 1T seagate 7200rpm 16 mb cache, 8gb memory. Window Vista Home Premiun 64 bit.
I am using this PC exclusively to run Photoshop CS3, I not runnig other application.I have a Partition Hard Drive of 35Gb specially for scratch disk.
My system indicate that I have 8gb ram, but in Photoshop Preference, Performance, only show 3.4gb.
Can you tell me why I have only 3.4gb? -
Photoshop CC Memory Leak / Exhausting RAM etc
I've recently signed up for CC and Photoshop, whilst looking beautiful - is taking up a ridiculous amount of memory. As I speak, it's just short of 5GB. This never happened with previous versions and I'm just wondering if there's a reason for this and if I can fix it?. I'm running the 64 bit version. I have 8GB of ram on my iMac.
Any help would be much appreciated.I also have problems regarding out of memory in PS CC. In my current workflow, I do choose my pictures in Adobe Lightroom where select edit in Adobe Photoshop CC. That pic has a resolution 5184X3465 pixel 21MB in size (Canon Raw). My Photoshop CC has no Third Party plugins. After that chosen pic is loaded in Photoshop CC, I can not do anything. Every operations is followed by out of memory. Even a simple brush stroke is not possible.
Wiping cache didn't have any effect. I also tried to alocate lesser ram (my rig: Win-8 64-Bit 12GB-Ram) about 4GB and has the same problem. PS CC Info shows: Dok.102,5/205,0 MB; RAM: 4,90GB/4,00GB; Effizienz:100%*
It seems, PS CC has reseverd the RAM as it should, but doesn't handle it right. Opening the picture without Adobe Lightroom worked without problem. I hope I can help with this Informations:
My Systeminformation:
Adobe Photoshop Version: 14.1.1 (14.1.1 20130910.r.414 2013/09/10:23:00:00) x64
Betriebssystem: Windows 8 64-Bit
Version: 6.2
Systemarchitektur: Intel CPU-Familie:6, Modell:10, Stepping:9mit MMX, SSE (ganze Zahl), SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, Hyper-Threading
Physischer Prozessor: 4
Logischer Prozessor: 8
Prozessor-Taktfrequenz: 3392 MHz
Eingebauter Speicher: 12228 MB
Freier Speicher: 6761 MB
Für Photoshop verfügbarer Arbeitsspeicher: 10859 MB
Von Photoshop verwendeter Arbeitsspeicher: 44 %
Bildkachelgröße: 1024 KB
Bildcache: 8
Anzeige: 1
Anzeigebegrenzungen: oben= 0, links= 0, unten= 1080, rechts= 1920
Mit OpenGL zeichnen: Aktiviert.
OpenGL – alte GPUs zulassen: Nicht erkannt.
OpenGL-Zeichnungsmodus: Erweitert
OpenGL – normalen Modus zulassen: Wahr.
OpenGL – erweiterten Modus zulassen: Wahr.
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=1536
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
gpu[0].RendererID=4485
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.2049"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20130621000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLSupported=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="4.2.1"
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="1.30 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
Seriennummer: 90970108608633791897
Anwendungsordner: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
Pfad für temporäre Dateien: C:\Users\BJRNBU~1\AppData\Local\Temp\
Der virtuelle Speicher von Photoshop hat asynchronen E/A aktiviert
Arbeitsvolume(s):
C:\, 918,8 GB, 581,0 GB frei
Ordner für erforderliche Zusatzmodule: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Required\Plug-Ins\
Primärer Zusatzmodul-Ordner: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Plug-ins\
Installierte Komponenten
ACE.dll ACE 2013/07/14-12:09:50 79.543790 79.543790
adbeape.dll Adobe APE 2013/02/04-09:52:32 0.1160850 0.1160850
AdobeLinguistic.dll Adobe Linguisitc Library 7.0.0
AdobeOwl.dll Adobe Owl 2013/03/03-12:10:08 5.0.13 79.533484
AdobePDFL.dll PDFL 2013/03/13-12:09:15 79.499517 79.499517
AdobePIP.dll Adobe Product Improvement Program 7.0.0.1786
AdobeXMP.dll Adobe XMP Core 2013/03/13-12:09:15 79.151481 79.151481
AdobeXMPFiles.dll Adobe XMP Files 2013/03/13-12:09:15 79.151481 79.151481
AdobeXMPScript.dll Adobe XMP Script 2013/03/13-12:09:15 79.151481 79.151481
adobe_caps.dll Adobe CAPS 7,0,0,21
AGM.dll AGM 2013/07/14-12:09:50 79.543790 79.543790
ahclient.dll AdobeHelp Dynamic Link Library 1,8,0,31
aif_core.dll AIF 5.0 79.534508
aif_ocl.dll AIF 5.0 79.534508
aif_ogl.dll AIF 5.0 79.534508
amtlib.dll AMTLib (64 Bit) 7.0.0.169 BuildVersion: 7.0; BuildDate: Mon Apr 8 2013 2:31:50) 1.000000
ARE.dll ARE 2013/07/14-12:09:50 79.543790 79.543790
AXE8SharedExpat.dll AXE8SharedExpat 2011/12/16-15:10:49 66.26830 66.26830
AXEDOMCore.dll AXEDOMCore 2011/12/16-15:10:49 66.26830 66.26830
Bib.dll BIB 2013/07/14-12:09:50 79.543790 79.543790
BIBUtils.dll BIBUtils 2013/07/14-12:09:50 79.543790 79.543790
boost_date_time.dll DVA Product 7.0.0
boost_signals.dll DVA Product 7.0.0
boost_system.dll DVA Product 7.0.0
boost_threads.dll DVA Product 7.0.0
cg.dll NVIDIA Cg Runtime 3.0.00007
cgGL.dll NVIDIA Cg Runtime 3.0.00007
CIT.dll Adobe CIT 2.1.6.30929 2.1.6.30929
CITThreading.dll Adobe CITThreading 2.1.6.30929 2.1.6.30929
CoolType.dll CoolType 2013/07/14-12:09:50 79.543790 79.543790
dvaaudiodevice.dll DVA Product 7.0.0
dvacore.dll DVA Product 7.0.0
dvamarshal.dll DVA Product 7.0.0
dvamediatypes.dll DVA Product 7.0.0
dvaplayer.dll DVA Product 7.0.0
dvatransport.dll DVA Product 7.0.0
dvaunittesting.dll DVA Product 7.0.0
dynamiclink.dll DVA Product 7.0.0
ExtendScript.dll ExtendScript 2013/03/21-12:10:31 79.535742 79.535742
FileInfo.dll Adobe XMP FileInfo 2013/03/19-12:09:02 79.151561 79.151561
filter_graph.dll AIF 5.0 79.534508
icucnv40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
icudt40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
imslib.dll IMSLib DLL 7.0.0.116
JP2KLib.dll JP2KLib 2013/02/19-12:28:44 79.248139 79.248139
libifcoremd.dll Intel(r) Visual Fortran Compiler 10.0 (Update A)
libiomp5md.dll Intel(R) OMP Runtime Library 5.0
libmmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 12.0
LogSession.dll LogSession 2.1.2.1785
mediacoreif.dll DVA Product 7.0.0
MPS.dll MPS 2013/03/15-13:25:52 79.535029 79.535029
msvcm80.dll Microsoft® Visual Studio® 2005 8.00.50727.6910
msvcm90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcp100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcp80.dll Microsoft® Visual Studio® 2005 8.00.50727.6910
msvcp90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcr100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcr80.dll Microsoft® Visual Studio® 2005 8.00.50727.6910
msvcr90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
PatchMatch.dll PatchMatch 2013/06/11-12:08:08 79.542390 79.542390
pdfsettings.dll Adobe PDFSettings 1.04
Photoshop.dll Adobe Photoshop CC CC
Plugin.dll Adobe Photoshop CC CC
PlugPlugOwl.dll Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit) 4.0.1.34
PSArt.dll Adobe Photoshop CC CC
PSViews.dll Adobe Photoshop CC CC
SCCore.dll ScCore 2013/03/21-12:10:31 79.535742 79.535742
ScriptUIFlex.dll ScriptUIFlex 2013/03/21-12:10:31 79.535742 79.535742
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, 1, 2012, 1003
tbbmalloc.dll Intel(R) Threading Building Blocks for Windows 4, 1, 2012, 1003
updaternotifications.dll Adobe Updater Notifications Library 7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME) 7.0.1.102
WRServices.dll WRServices Mon Feb 25 2013 16:09:10 Build 0.19078 0.19078
Erforderliche Zusatzmodule:
3D Studio 14.1.1 (14.1.1 x001)
Adaptive Weitwinkelkorrektur 14.1.1
Aquarell 14.1.1
Arithmetisches Mittel 14.1.1 (14.1.1 x001)
Basrelief 14.1.1
Bereich 14.1.1 (14.1.1 x001)
Bildpaket-Filter 14.1.1 (14.1.1 x001)
Blendenflecke 14.1.1
BMP 14.1.1
Buntglas-Mosaik 14.1.1
Buntstiftschraffur 14.1.1
Camera Raw 8.2
Camera Raw-Filter 8.2
Chrom 14.1.1
Cineon 14.1.1 (14.1.1 x001)
Collada 14.1.1 (14.1.1 x001)
CompuServe GIF 14.1.1
Conté-Stifte 14.1.1
De-Interlace 14.1.1
Diagonal verwischen 14.1.1
Dicom 14.1.1
Differenz-Wolken 14.1.1 (14.1.1 x001)
Distorsion 14.1.1
Dunkle Malstriche 14.1.1
Durchschnitt berechnen 14.1.1 (14.1.1 x001)
Eazel Acquire 14.1.1 (14.1.1 x001)
Entropie 14.1.1 (14.1.1 x001)
Erfassungsbereich 14.1.1 (14.1.1 x001)
Extrudieren 14.1.1
Farbpapier-Collage 14.1.1
Farbraster 14.1.1
Fasern 14.1.1
FastCore-Routinen 14.1.1 (14.1.1 x001)
Feuchtes Papier 14.1.1
Filtergalerie 14.1.1
Flash 3D 14.1.1 (14.1.1 x001)
Fluchtpunkt 14.1.1
Fotokopie 14.1.1
Fotos freistellen und gerade ausrichten (Filter) 14.1.1
Fotos freistellen und gerade ausrichten 14.1.1 (14.1.1 x001)
Fresko 14.1.1
Für Web speichern 14.1.1
Gekreuzte Malstriche 14.1.1
Gerissene Kanten 14.1.1
Glas 14.1.1
Google Earth 4 14.1.1 (14.1.1 x001)
Grobe Malerei 14.1.1
Grobes Pastell 14.1.1
HDRMergeUI 14.1.1
IFF-Format 14.1.1
JPEG 2000 14.1.1
Kacheleffekt 14.1.1
Kacheln 14.1.1
Kanten betonen 14.1.1
Kohleumsetzung 14.1.1
Konturen mit Tinte nachzeichnen 14.1.1
Körnung & Aufhellung 14.1.1
Körnung 14.1.1
Kräuseln 14.1.1
Kreide & Kohle 14.1.1
Kreuzschraffur 14.1.1
Kristallisieren 14.1.1
Kunststofffolie 14.1.1
Kurtosis 14.1.1 (14.1.1 x001)
Leuchtende Konturen 14.1.1
Malgrund 14.1.1
Malmesser 14.1.1
Matlab-Vorgang 14.1.1 (14.1.1 x001)
Maximum 14.1.1 (14.1.1 x001)
Median 14.1.1 (14.1.1 x001)
Mehrprozessorunterstützung 14.1.1 (14.1.1 x001)
Mezzotint 14.1.1
Minimum 14.1.1 (14.1.1 x001)
Mit Struktur versehen 14.1.1
Mit Wasserzeichen versehen 4.0
MMXCore-Routinen 14.1.1 (14.1.1 x001)
Neigung 14.1.1 (14.1.1 x001)
Neonschein 14.1.1
NTSC-Farben 14.1.1 (14.1.1 x001)
Objektivkorrektur 14.1.1
Objektivunschärfe 14.1.1
Ölfarbe 14.1.1
Ölfarbe getupft 14.1.1
OpenEXR 14.1.1
Ozeanwellen 14.1.1
Patchwork 14.1.1
PCX 14.1.1 (14.1.1 x001)
Pfade -> Illustrator 14.1.1
Photoshop 3D-Modul 14.1.1 (14.1.1 x001)
Photoshop Touch 14.0
Pixar 14.1.1 (14.1.1 x001)
PNG 14.1.1
Polarkoordinaten 14.1.1
Portable Bit Map 14.1.1 (14.1.1 x001)
Prägepapier 14.1.1
Punktieren 14.1.1
Punktierstich 14.1.1
Radialer Weichzeichner 14.1.1
Radiance 14.1.1 (14.1.1 x001)
Rasterungseffekt 14.1.1
Risse 14.1.1
Schwamm 14.1.1
Schwingungen 14.1.1
Selektiver Weichzeichner 14.1.1
Solarisation 14.1.1 (14.1.1 x001)
Spritzer 14.1.1
Standardabweichung 14.1.1 (14.1.1 x001)
Stempel 14.1.1
STL 14.1.1 (14.1.1 x001)
Strichumsetzung 14.1.1
Strudel 14.1.1
Stuck 14.1.1
Sumi-e 14.1.1
Summe 14.1.1 (14.1.1 x001)
Targa 14.1.1
Tontrennung & Kantenbetonung 14.1.1
Unterstützung für Skripten 14.1.1
Varianz 14.1.1 (14.1.1 x001)
Variationen 14.1.1 (14.1.1 x001)
Verbiegen 14.1.1
Verflüssigen 14.1.1
Versetzen 14.1.1
Verwackelte Striche 14.1.1
Verwacklung reduzieren 14.1.1
Wasserzeichen anzeigen 4.0
Wavefront|OBJ 14.1.1 (14.1.1 x001)
Weiches Licht 14.1.1
Wellen 14.1.1
WIA-Unterstützung 14.1.1 (14.1.1 x001)
Windeffekt 14.1.1
Wireless Bitmap 14.1.1 (14.1.1 x001)
Wölben 14.1.1
Wolken 14.1.1 (14.1.1 x001)
Optionale Zusatzmodule und Zusatzmodule von Drittanbietern: KEINE
Nicht geladene Plug-Ins: KEINE
Blitz:
Mini Bridge
Kuler
Adobe Exchange
Installierte TWAIN-Geräte: OHNE -
Photoshop CS6 memory leak when idle and nothing open
Photoshop CS6 runs away with memory after being used and then going idle. If I open up PS and leave it, it will be ok but as soon as I open any file it will go up in memory usage (which is normal) but when I close all files and hide PS the memory will stay high never goes back down. When I close PS and re-open (no files open) again it idles at 300Mb memory but when I open a file then close it and then hide/idle PS it raises and stays around 1.25-1.5 GB if not more.
I have tried to Purge All, and even hide all menus to no avail. I have even tried to close Suitcase (eleminiate any font issues) and still same problem. I am running PS bone stock, no extra plug-ins.
Any ideas on why it would be doing this would be greatly appreciated!
My Computer:
Photoshop 13.0.1
MacBookPro
OS 10.6.8
CPU: 2.66 GHz Intel Core 2 Duo
Mem: 4 GB 1067 MHz DDR3
HD: 300GB (30GB Free)Photoshop is not supposed to free memory when you close documents -- that's normal, because the memory gets reused.
Yes, opening a file makes the memory usage go up - because space is needed for the document and it's window.
None of what you said describes a leak, and sounds like perfectly normal behavior. -
Photoshop CS6 Memory Leaking Problem
Adobe CS6 extended is using between 3.1GB - 9.8GB of ram.
It doesn't stop when i close all the psd files, only frees up when i close the program.Open Photoshop. Photoshop (Mac) or Edit (Windows) > Preferences > Performance. Reduce the Allocated memory (RAM) for Photoshop.
-
Photoshop CC is a Memory Hog ... I have 4GB and PS CC is the only thing open my ram drops to like 895mb free...
Definitely more RAM would be ideal -- but only useful with a 64-bit OS. You can adjust the amount of memory the OS will allow PS to use in Photoshop Preferences > Performance if you need to work with the system config you have and need ram allocation change to help with performance problems with PS or other applications.
You might find this article of interest (written for CS6 but should generally apply for CC).
http://blogs.adobe.com/crawlspace/2012/10/how-to-tune-photoshop-cs6-for-peak-performance.h tml -
Problema permisos al abrir photoshop CS6 (memoria virtual)
Hola, he instalado photoshop CS6 en un portátil con una instalación limpia de Windows 8 y justo al arrancar da un error de memorial virtual que solo he podido resolver abriendo el programa como administrador.
El error que aparece es:
No se ha podido abrir un archivo de memoria virtual virtual porque el archivo está bloqueado, no tiene los permisos de acceso necesarios u otro programa está usando el archivo...
Ya sé que el problema es de privilegios, lo he visto en alguna otra pregunta lo cual he podido comprobar porque si le doy entrar como administrador sí que entra, la pregunta es qué tengo que cambiar para no tener que entrar como administrador (los usuarios del pc tienen que poder abrirlo sin tener permisos de administrador ni conocer la contraseña).
Gracias y saludos.Primera vez que comento en este foro, tuve el mismo problema y consegui la solución en otro foro, aproposito la respuesta es del 2008 y por tanto pense que no funcionaría.
El usuario dice:
"cuantas particiones tienes?
el photoshop usa una determinada cantidad de espacio en tu disco duro C q se llama memoria virtual, al tener solo C tendras esos problemas porque tu memoria virtual sera muy poca, por eso es necesatrio que tengtas particiones para que puedas asignarlas como disco de memoria virtual..
si ya tienes particiones(C:/ , D:/ , E:/ , F:/ ,...etc)
solo tienes que asignarlas como memoria virtual en el photshop
abres el photoshop y vas a:edicion/ preferencias/ plugins y discos de memoria virtual.. y eliges como primer disco de memoria virtual a la particion mas lejana ( por ejemplo F, luego E,.. D y por ultimo eliges C...)
con eso ya es suficiente para no tener esos problemas.. "
PD: Para configurar las preferencias debes ingresar como Administrador.
Espero que sirva a muchos.
Fuente: http://www.photoshop-designs.com/foro/viewtopic.php?t=27683 -
Photoshop CS3 memory release problem
Hi,
I have been working on a large group of DNG's and I'm noticing that as I proceed through the edits my computer memory seems to be 'not releasing'. Example: Select photo, process it in RAW, open it in Photoshop CS3, edit, save and CLOSE the image. My computer memory does not seem to be refreshed when I close the image and eventually, after several images, I have to close the application to retrieve the memory. I am running on a PC Vista with 3 gig of memory (max my operating system will work with).
If anyone has suggestions, I would appreciate them.
Thanks,
J.It won't use only 75%, either. It
i allocates (i.e. reserves)
75% at opening if prefs are set that way, but will use all the RAM that the system has available if necessary. That's the reason you don't set ridiculous memory allocations of 90-100% in prefs (unless you have more than 2GB of RAM, which is PS current maximum) - there's no free RAM for the system to use after Ps launches in that case, so only virtual memory remains for the system and everything will slow or crash.
Once PS has used all available RAM (not only its allocated RAM), then it will start writing scratch - which is also set up and waiting at opening. I'm assuming PS was set up this way for initial speed - if it has RAM already allocated at opening it will not have to waste processor time calling for RAM.
It took me a while to get around the concept of all this, but I think I understand it now - it is in fact very well thought out for maximum speed and stability. -
Wait for ages as Photoshop measures memory with Premiere running.
I have recently upgraded to CS6 and all is good so far however I often need to use Photoshop with Premere but wait ages when I fire up Photoshop "photoshop is measuring Memory"? why the massive delay?
Rod
Window 7
8 GIG Memory
Rampage 3 extreme motherboard
Nvidea GForce 570 GTXhttp://forums.adobe.com/community/photoshop
-
i.m trying to save a file in photoshop 3000ppi 16RGB in .jpeg and it.s taking all my 16GB and it.s showing not enough ram memory, i.ve installed and reinstalled photoshop and it.s still showing the same message, i spoke to apple and they told me shouldn.t take all ram memory maximum 2GB....
Could you please go to Image > Image Size and post a screenshot of that dialog? I need a more clear picture of what you have.
Also is it CMYK or RGB mode? Also 3000 ppi is really unusual. Press quality is about 300 ppi.
Are you saving for print or web? Tiff or PSD is proper for print, not jpeg. That would be for a small file like I have shown here going to display on the web.
Example: -
PS currently takes 1.7GB of memory AFTER I have closed all the files. I have no plugins. The only thing that helps is restarting PS. Any thoughts? thanks
Thanks for the help. I am still a little confused. I did a search on "history, undo stack, temp memory" and nothing came up. Could you just tell me logic then?
I don't understand:
The memory will be reused - and AFAIK released if the OS requests it.
This is all for speed reasons.
It is never released and it absolutely does slow down my computer. Previous versions of PS never did this. -
thinking about the following purchase
windows vista home premium 64
intel 2 duo e7500 [2.93ghz, 3mb l2, 1066mhz fsb]
8gb ddr3-1066mhz sdram [4 dimms]
512mb ati radeon hd 4350
640gb 7200 rpm,sata 3gbs
currently have samsun syncmaster 220wm and considering hp w2558hc monitor
will this suffice for smooth operation of photoshop cs4
thank you
jimThat'll handle it.
Better to get at least 2 hard drives though* and I'd go for an Eizo monitor.
* It pays to keep the Photoshop scratch drive separate from the system drive to avoid conflicts.
I also have a 3rd drive for data storage. -
Plug-in request to release memory in Photoshop
Photoshop has never released memory. I read about 10 discussions about it, with entertaining side-steps to virus scanners and video drivers, and it all comes down to the same thing. Photoshop does not release memory. As Adobe knows this since a couple versions back and never patched or updated it in a new release, it would therefore be great if some company could pick up the task to write a plug-in for this. Almost every serious Photoshop user will buy that plugin as the only other option is to buy more memory.
Just a little illustration for newcomers what the problem is. Here's what Photoshop uses according to the task manager:
start Photoshop -> 110mb
open a 2.65gb psb -> 7975mb
close the 2.65gb psb -> still 7975mb
open a different 2.07gb psb -> 10106mb and any edit goes tedious slow because it is partly scratching because it did not release the memory when closing the 2.65gb file. The only solution was that I had to restart Photoshop after I closed the first psb. This is by the way with 16gb ram on win 7 64, where photoshop is assigned 10gb (67%).
The same thing happens if you Automate a Batch because with every opened file the memory never is given back until Photoshop ends up on the scratch disc slowing down to about one third the original speed if it isn't slower.
Anyway, I really hope there are some talented coders out there, using Photoshop, who would want to developer a plug-in. I have 16gb ram in my computer and the only program that uses that is Photoshop. I would have never upgraded my ram if Photoshop released memory.Why do you think it needs to work differently than it does? What specific problem are you having?
If you want the best possible Photoshop performance, having it allocate then reuse its own memory (without deallocation) is more efficient than returning it to the operating system, then requesting it again later. It doesn't sound right at first, but the Adobe engineer Chris Cox has said that they've explicitly tried it the other way and it just doesn't work as well. Your basic assumption (that Photoshop is doing something wrong) is simply flawed.
Now, if you need your system to be doing a number of RAM-intensive things at the same time, including Photoshop, you have to outfit it with sufficient RAM that it can work with Photoshop using all that you have allowed (in the Performance preferences) PLUS the other RAM usage you anticipate. In reality, few folks use multiple applications simultaneously that are all RAM-intensive, and those who do simply buy huge amounts of it. I personally outfitted my system with 48GB and it's never starved for RAM (and I do multitask a lot).
There's little hope for a plug-in that will cause Photoshop to release all of its RAM. The only way I know of for a plug-in to affect Photoshop's memory usage, and that is to provide a large (up to 2GB because it's a signed 32 bit field) estimate of how much RAM a plug-in will need in the gFilterRecord->bufferSpace field. That field is 32 bits no matter whether the 32 bit or 64 bit Photoshop is running, so the most a plug-in could possibly ask Photoshop to release (indirectly) is 2GB.
-Noel -
Trying to load quickbooks 2013, says I need 1GB to load but only have 767MB, computer has 5GB memory
Quickbooks 2013 says that I do not have enough memory to load the software but the computer has 5 times as much memory as needed. How to I get the software to load?
Hey duck2013,
The memory that Quickbooks is referring to is the space available on your hard drive.
Are you saying that you have 5GB of RAM memory? or 5GB of free hard drive space?
It would help to know your product number so I can look at your specifications. Here are the steps to find your product number.
I'll keep an eye out for your reply -
Ok now i cant figure this out. i installed the recent security update and now things are going screwy. i go to open up photoshop and it wont open. the dock icon bounces then goes away leaving me wondering whats going on. I uninstalled and re installed the whole Creative Suite but photoshop still wont budge. It was working just fine before the security update and now i duno what. is this to blame or is there something else?
Ok, I got this right from the source, so ideally it will work. OK
Follow the directions, repost and let me know
MAC OS10:
First, be sure to BackUp your data, then run Mac Software Update (located in System Preferences) to bring the Operating System (OS) and Mac firmwares up to date. And run all the Adobe Updaters adobe.com.
Ruling out the User account and routine maintenance are the first steps in troubleshooting crash freeze stability problems, including setting up clean User Account, and using Disk Utility to Repair Disk and Repair Permissions, Safe Boot, and running fsck -y.
If the problem clears logged into a new "Spare User" account, a User's account preference is corrupted. If the problem does not clear in a new "Spare User" account, the problem is likely system wide, or hardware.
Rule out RAM gballard.net is also important troubleshooting. In addition to crashing, kernel panics, Type 1 Type 2 Type 3 errors, Unexpectedly Quiting, corrupted files and disk errors, typical symptoms of bad Ram in Photoshop include rows lines patches of bad pixels on screen that also print (the actual file is being corrupted). If the bad pixel areas are on the monitor, but do not print (the actual file is not corrupted), video card or video-card drivers are prime suspects. Remember, video cards also have flash firmwares to flash update.
Test Hardware Interface gballard.net for the hardware's ability to transfer data free of corruption on hard disk drive interfaces (such as SCSI, IDE, etc.). See the bottom of the linked page and DOWNLOAD Timothy A. Seufert's dctest. Dctest assumes that your CPU and memory and disk are working fine. There are OS9 and OSX versions in the download.
Bad Damaged Hard Drives:
If running Apple's Disk Utility's FirstAid Repair Disk and Repair Permissions, and the Mac's fsck -y Unix command cannot fix any all disk problems, I would recommend running third-party disk utilities BEWARE! gballard.net only as a last resort.
Bad Blocks apple.com on the hard drive can also cause a computer to be very unstable....
"Haxies," those free/shareware, application and user hacks that modify various System features, application programs and plug-ins, including bad fonts and font management gballard.net, are also prime SUSPECTS to troubleshoot and rule out, as are flaky video–card drivers. Check your video card manufacturer web site for video card firmware updaters, new drivers and compatibility issues.
Another thing to troubleshoot for is illegal Unix characters in the file names starting from the hard drive name down. These illegal characters may include: * ~ / + ! " é ñ ; : ) ? (see Mac and Windows OS File/Folder naming rules portfoliofaq.com for complete information). If you're using any illegal characters (or extra long names or spaces) in your naming hierarchy, try renaming them.
Photoshop CS and CS2 seems to be super sensitive to bad fonts, so be sure to rule out the fonts if you are having stability issues.
Troubleshooting Photoshop won't install, from the original Adobe Install CD, try copying the 'Adobe(R) Photoshop(R) Folder' (100 to 150 MB) to the desktop - this folder contains the installer and all its files. Eject the CD, and run the installer from the desktop.
This copy-installer-folder-to-hard-drive technique works on the Adobe installers that require us to verify an original full install CD (insert the full retail install CD, when the installer asks for it point it to the CD).
For troubleshooting specific numeric Mac OS error codes, try appleerrorcodes.com.
My most decisive TroubleShooting technique — Empty = Versatile gballard.net — is to Test on an OS–Suspect Level. In less than an hour, this method effectively rules out the hardware, the install and its other third–party issues.
Ann Shelbourne offers some sage font troubleshooting advice, Ann wrote:
Have you cleaned out your AdobeFnt.lst files recently?
Do a Search for "adobefnt" and delete all that you find — except for "AdobeFnt.db".
(Don't worry, they will re-create themselves as needed).
Have you ruled out conflicts between System fonts and your other fonts? (Ann continued)
Have you ran Cocktail?:
Launch Cocktail
Choose "Pilot"
Check everything on the first dialog and set to "Automatically: Restart"
Then click Options and check everything except "Cookies"
Return to main panel and click "RUN"
It will take just a few minutes and should improve performance.
Wade Zimmerman has found a quirky FIX for Photoshop CS (8.0) not opening, crashing on launching, under Panther 10.3.2, Wade wrote:
Try changing the time zone then change it back to the correct time zone that you are in but first trash your PS Preference, if that does not work try changing the City within the time zone and then change it back. Or some kind of combination. But again, each time trash PS preferences maybe even restarting the computer.
Ann Shelbourne added, if you are in the UK, don't choose GMT but choose your nearest city by name.
This sounds goofy — but it has worked for a lot of users.
+++
Also, Photoshop> Preferences> Memory & Image Cache:
Jeff Schewe, Adobe Photoshop expert, offers us the facts on Photoshop, Jeff writes:
Read this: Photoshop CS2-How much RAM? – Fact
http://photoshopnews.com/2005/04/04/photoshop-cs2-how-much-ram-fact/
When you get done and understand it, try reading: Memory allocation and usage (Photoshop CS2)
http://www.adobe.com/support/techdocs/320005.html/
And then read:
Improve performance in Photoshop CS2 on computers with more than 1 GB RAM
http://www.adobe.com/support/techdocs/331372.html/
My two cents on the subject:
Memory: Try setting 50 percent (no higher than 75 percent) for anything less than 2 GB RAM.
Over 2.5 giga bytes of RAM: The Mac OS limits all applications to maximum of 2 giga bytes of RAM. In other words, setting Photoshop's Memory setting to 100% will provide Photoshop with up to 2 GB memory, and leave the remaining 500 MB for the Operating System and other applications.
We do need to be careful to leave a cushion of unused RAM for whatever applications we run concurrently with Photoshop.
If we get a lot of OS 10's Spinning Beachball Color Wheel while using Photoshop, we probably need to install more RAM, or assign a lesser percentage of RAM to Photoshop. Seeing the BeachBall is normal for working on very large files (over 200 mega bytes) while Photoshop's ScratchDisks gballard.net catch up.
With over 3 giga bytes of installed RAM, I would start with a 100–percent Memory setting in Photoshop.
NOTE: Adobe is recommending the Ram/Memory issues for 2.5GB-plus work stations...if 100% Memory is not working optimally, as recommended above, try reducing down to a "safer" 75%, said Adobe's Chris Cox.
Cache Levels: Adobe is recommending setting this to 4 (for now because of an OS10.3.2/PS8.0 conflict). I generally set the Cache Level to 8 on newer machines, I recall CS2 is defaulting to 6.
Trashing Preferences:
If you're trying to rule out Photoshop corruption or reset Default settings, FIRST try trashing:
HardDrive> User> Library> Preferences> Adobe Photoshop 7.0 Settings folder.
HardDrive> User> Library> Preferences> com.adobe.Photoshop.plist file.
There are several other Photoshop preferences there you may trash.
Relaunch Photoshop.
If the problem has not cleared, Mac OS 10, Trash the following (and reinstall Photoshop):
HardDrive> Applications> Adobe Photoshop 7/CS folder.
HardDrive> User> Library> Preferences> Adobe Photoshop 7.0 Settings folder.
HardDrive> User> Library> Preferences> com.adobe.Photoshop.plist file.
Reinstall Photoshop.
Run all Photoshop Updaters adobe.com.
+++++
If the problem has not cleared after purging/reinstalling/updating Photoshop, the problem is likely outside of Photoshop in third–party, bad hardware or a corrupted install. At this point we generally need to Initialize/Erase/StartFromScratch gballard.net...a good opportunity to rethink Partitioning our disks for a Photoshop workflow gballard.net and implement a BackUp strategy gballard.net.
In severe cases — to prepare a Mac for a Apple Authorized Service Provider (AASP) — I follow my troubleshooting MELTDOWN procedure gballard.net. In addition to repairing any Bad Blocks, this procedure will be conclusive in a couple hours, plus the time it takes to ZeroWrite Write Zeros, if the problem is hardware or installed software or damaged hard drive....
+++++
BEFORE Initializing, Reformatting, Erasing:
SEARCH the Adobe Photoshop Mac Forum adobe.com , GoogleWeb.com, and GoogleGroups.com for key words for second opinions, known bugs, posted fixes, solutions and work arounds.
+++++
Maybe you are looking for
-
I need detailed explanation of the OC4J config/*.xml files.
Anybody know where I can find good descriptions of the OC4J config files?? I've found some stuff on www.orionserver.com but they aren't good enough. Specifically, I have someone who wants a <lib> entry made for his app into the server.xml file. I wan
-
Exporting images in PDF and broadcasting with custom template error in BI 7
Hello! We're in the process of creating broadcast reports and are running into some problems. We need someone with experience exporting PDF's or creating broadcasts using custom web templates in 7.0. Our issue is two-pronged: 1) We want users to be a
-
Hi All, While running the program - Periodic Account Statement (t-code F.27) u2013 in background(Program > Execute in background) 2 spool requests are generated. Why 2 spool requests are generated ? Only 1 spool request should get generated. Corresp
-
JMSBridgesXA/xa-compliant-oracleaq - how do TX work? StartupClass questions
Hallo all, yesterday we called in our (very simple) MDB sessionContext.setRollbackOnly(). Expected behavior: Oracle AQ should resend the JMS message after a while (queue_table still needs to have the message). Seen behav
-
I purchased a video and it keeps telling me "cannot download at this time" but it has been charged on my itunes card