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

Similar Messages

  • 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 CS6 memory leak?

    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.

  • Mail.app memory leak. RAM use increases until system is no longer usable

    I am having this problem since a week ago more less.
    Mail keeps increasing the memory use from a starting 100 Megas. Increasing something like 100 megas each 10 minutes, until the whole system is unresponsive.
    Any ideas?
    Thanks!
    PD: I have 3 IMAP accounts and 1 POP. In total 3348 messages. Running 10.5.4

    Thank for the fast reply!
    Indeed it happened to me. Whenever I dropped a file to the icon it would just hang up the computer. Then I removed my custom plugins (3 columns plugin, and Encryption plugin , I thing). And it worked well. Or at least I could drop files to the Mail Dock icon.
    My impression is that it might be related with IMAP and Gmail. I have 3 Gmail accounts. One of them is my primary email account, it has many many mail. The "all Mail" folder is a big one and probably Mail is trying to catch everything. It does so slowly in the background, creating the problem. May be. Just in case I selected the option not to download attachment in mails.
    Other suspect is the iGTD program I have been using. It syncs with Calendar and the ToDo folder in Mail. But the problem is still there even if iGTD is not working.
    I remember reading something about email with attachment that had numbers on the title, or something like that. It would create a similar problem but I can´t find it now.
    I have tried to control the output from "lsof | grep Mail" and "fs_usage -w -f filesys Mail" but I can´t find anything suspicius (not that I am an expert on that, though)
    THANKS a lot for the help.

  • Apparent Photoshop Memory Leak

    Over the last couple months I have been having what seems to be a memory leak problem with Photoshop. I'll be working on a document nice as can be, my screen will freeze, go black, then return with my graphics drivers telling me that it has just recovered from a failiure. At this time photoshop will not respond, and I am forced to close it, and lose all the work I have done.
    The crashes usually happen when I am transforming objects, however it has happened while using vector, and raster tools like the pen, and brush.
    I have been having this problem ever since I switched laptops from an Acer Aspire (Pentium 6 integrated win8 4gb RAM), to an Acer V3 (AMD A10 amd radeon 7660m win8 6gb RAM). On my last laptop that was noticably worse in terms of hardware, with this new laptop I've been having worse problems.
    I use CS6 on both systems.
    I have up to date graphics drivers, and I have updated photoshop to the latest patch (as of 16th December).
    I am also not able to limit the amount of vram photoshop is allowed to use through the preferences, and it keeps resetting itself (every time the program crashes).
    Part of me wants to blame the AMD APU that's in their A10 CPU, but I am not able to pin it on that system just yet.

    xzenocrimzie wrote:
    I have up to date graphics drivers
    With an ATI card, unfortunately that's not the right approach.  AMD has fallen on its face lately.  Maybe they lost the guy who knows what he's doing, I don't know.
    Try switching Photoshop's advanced GPU setting to Basic, and close and restart Photoshop.
    If you've already done that, and it's not working, seek out Catalyst 12.8 and see if it's available for Windows 8.  That's a decent (though not perfect) recent version.  You'll have to uninstall the current version first in order to install the earlier one.
    I have some hope for 12.12, but so far they've been completely unresponsive to my reports of problems with 12.10 and the newer betas.  Apparently the Adobe engineering people can't get them to move on these problems either.  Somehow it seems Windows 8 caught them off guard, even though Microsoft had released all those previews.  But don't fret; 12.10 and newer don't work worth a darn in Windows 7 either.
    -Noel

  • Firefox 4 still suffering from a serious memory leak, ends up using 2GB of RAM on 5 tabs and a few plugins?!!

    Why does even Firefox 4, which was supposed to have this issue fixed by now, still suffer from memory leaks?
    I opened up 4-5 tabs, enabled Firebug to tweak a few pages, and an hour later Firefox usage is up to 2GB of RAM?
    What a...?!
    Now, seriously, if you run to suggest that it is most likely due to add-ons and that I should disable them all and start Firefox in safe mode, let me just cut you off right there and ask you this - out of millions of people who downloaded this browser, who the hell uses it without any plugins and/or in safe mode?
    If you're gonna make a browser, make it so that it's lean and free of these issues to begin with, out of the box AND in case an addon or something else is added to it - can't they protect the core files and libraries from being victims to this, in case the addons are to blame?
    And in case it's a Firefox issue to start off with, seriously, can you get a dedicated developer to look into this alone and get it fixed, once and for all?

    I have six tabs open and generally have 3-5. It's been sitting here since last night. I'm using 296Mb ram which is high for me on Windows. My wife and son both use FF4 also and, having just checked, are between 210 and 268Mb respectively.
    No one I know ever complains about high memory usage in FF4 and neither have I experienced it since FF2.5 when memory leaks any user would notice were all fixed.
    So my advice is the same. If your add-ons aren't causing you problems, fix your system.

  • Still memory leaks with 10.8.4

    I hoped 10.8.4 could solve the issue..
    Unfortunately I still have memory leaks, pages out and inactive memory full for a lot of programs running. First of all FCX importing and transcoding full the inactive memory, and OSX slows down, swapping to the SSD. The same problem with all (4 in total) macs mounting ML.
    Has anyone solved the problem please?
    Thanks in advance.
    Attilio

    Attilio, although I'm not a Final Cut user, I suspect that your problem is, as Kappy first said - insufficient RAM.
    See: http://forums.macrumors.com/showthread.php?t=1332888 for instance.
    It's a RAM hog. With the Retina, you're stuck with the RAM you've got now, unfortunately. With any other hardware, I'd consider boosting the RAM as much as you can. I don't run FCX or any video editing software (I build web sites - so I use Dreamweaver, Photoshop, Lightroom etc.) and I boosted the RAM in my Mac Pro to 18GB quite a while ago because I was seeing a lot of pageouts and slowdowns with 10GB. I do tend to have a ton of windows and apps open at once.
    See also: https://discussions.apple.com/thread/4759586?start=0&tstart=0 - Kappy's very good explanation of memory usage and various links to check.
    Whether it appeared to run better in SL or not, I can't really say - unless you ran two identical Macs, side by side doing exactly the same things in FCX with the two operating systems installed, I don't know how one could accurately assess that.

  • How to fix huge iTunes memory leak in 64-bit Windows 7?

    iTunes likes to allocate as much as 1.6GB of memory on my dual-quad XEON 8GB 64-Bit Windows computer and then becomes unresponsive.
    This can happen several times a day and has been going on for as long as I can remember.  No other software that I use does this - only Apple's iTunes.  Each version I have installed of iTunes appears to have this same memory leak.  Currently I am running version 10.7.0.21.
    I love iTunes when it works.  But having to constantly kill and relaunch the app throughout the day is bringing me down.
    Searching for a fix for this on the internet just surfaces more and more complaints about this problem - but without a solution.
    Having written shrinkwrapped software for end users as well as for large corporations and governments for more than 25 years I know a thing or two about software.  A leak like this should take no more than a day or two to locate using modern software tools and double that to fix it.  So why with each new version of iTunes does this problem persist?  iTunes for Windows is the flagship software product Apple makes for non-Mac users - yet they continue to pass up each opportunity they have had over the years with each new release to fix this issue.  Why is this?
    Either the software engineers are not that good or they have been told NOT to spend time on this issue.  I personally believe that the engineers at Apple are very good, and therefore am left thinking that the latter is more likely the case.  Maybe this is to coax people to purchase a Mac so that they can finally run iTunes without these egregious memory leaks.  I would like to offer another issue to consider.
    Just as Amazon sold Kindles and Google sold Nexus tablets at low cost - not counting on margin for profit - but instead they wanted to saturate the marketplace with tools for making future purchases of content almost trivial to do with their devices.  Apple also counts on this model with their pricer hardware - but they also have iTunes.  Instead of trying to get people to switch to a MAC by continuing to avoid fixing this glaring issue in iTunes for Windows I would like to suggest that by allowing their engineers to address this issue that Apple will help keep Windows users from jumping ship to another music app.  The profit to be made by keeping those Windows users happy and wedded to the iTunes store is obvious.
    By continuing to keep this leak in iTunes for Windows all it does is lower my esteem for the company and start to make me wonder if the software is just as buggy on Macs.

    I have same issue. Ongoing for more than 1 year and currently running iTunes 11.3.
    My PC is Dell OptiPlex 990 I7 processor, 8GB ram, W7 64 [always keep things patched up to latest OS updates etc]
    I use this iTunes install to stream music videos etc to multiple appleTVs, ipads, iphones etc .. via Home Sharing
    Store all my media including music, videos and apps on separate NAS  .. so the iTunes running on PC is only doing the traffic cop role and streaming / using files stored on NAS .. creates lots of IO across my network
    Previous troubleshooting suggest possible contributing causes include
    a) podcast updates  .. until recently I had this auto updates on multiple podcast subscriptions, presumably the iTunes would flow this from the PC to save on the NAS across the network .. if the memory leak is in the iTunes network communication layer (?bonjour?)  this may be sensitive to IO that would not normally occur if the iTunes file saving was local on the same PC
    b) app updates .. have 200+ apps in my library and there is always a batch of updates .. some updates 100s of MB is size .. routinely see 500MB to 1GB of updates in single update run .. all my apps are
    c) streaming music / movies .. seems when we ramp up streamlining of music or movies . memory leak grows faster .. ie within hours of clean start
    c) large syncs of music or videos to ipads or iphones .. noticed that get big problems when I rebuild an ipad .. I typically have 60+ GB of data in terms of apps /  music / videos to load .. have to do rebuild in phases due to periodic lockups

  • Memory leak in solaris 9

    Hi ,
    I have Oracle9i database running on Solaris 9. After every 6 days my solaris box went out of space although its a test box and there is no activity on the system. Why the hell it takes all the ram and swap space when there is no activity on the system except Oracle Instance is running with no user connection. What process are running in the background that takes all the memory and i have to restart this box every week. IS THERE ANT PATCH OF MEMORY LEAK FOR SOLARIS9?. I am not a solaris administrator and i have to fix this problem before moving my system to production. I would really appreciate your help.
    Thanks.

    Hi ,
    I have Oracle9i database running on Solaris 9. AfterI have had for some months been running oracle 9i (and 8i) under solaris 9. There have been no problems and the server has been stable.
    It sounds like you may have misconfigured the solaris kernel. It also sounds like your SGA is too large to fit in memory.
    So I guess the first step would be to check the SGA and then the /etc/system file.
    Here is what mine looks like for example:
    SQL> show sga
    Total System Global Area 219644872 bytes
    Fixed Size 730056 bytes
    Variable Size 167772160 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 811008 bytes
    SQL>
    bash-2.05$ tail /etc/system
    set shmsys:shminfo_shmmax=4294967296
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=100
    set shmsys:shminfo_shmseg=10
    set semsys:seminfo_semmni=100
    set semsys:seminfo_semmsl=256
    set semsys:seminfo_semmns=1024
    set semsys:seminfo_semopm=100
    set semsys:seminfo_semvmx=32767
    bash-2.05$
    bash-2.05$ vmstat
    kthr memory page disk faults cpu
    r b w swap free re mf pi po fr de sr dd dd f0 s0 in sy cs us sy id
    0 0 0 2076240 1302024 0 1 1 0 0 0 0 0 4 0 0 411 92 135 0 1 99
    bash-2.05$
    You need to gather more system information to help you troubleshoot.

  • FIrefox betrayed by its own "developers"? Memory Leak Work Around at Bottom

    Firefox SUCKS memory and holds onto it. Try this test: Open it, leave ONE tab, open and sit back and and watch the damn thing crash.
    Funny, as soon as the project people started getting so much money from Google that they had to restructure to avoid losing its non-profit status Firefox developed an insatiable thirst for RAM that has only gotten worse in the YEARS since. They won't fix the problem, they won't acknowledge the problem, the ignore every post about it . . . . So, is killing FF's user base the price for the continued Google money that they so quickly whored themselves out for? Has FF been run by Google these last few years? They certainly couldn't wreck any better.
    Posted by Wahoo at https://support.mozilla.org/en-US/questions/939920
    "Using ADD-ons to remove memory leak. Mozilla says to remove add-ons to fix leak. Firefox sucks memory. it always has and always will. Nobody wants to admit it exsists on the Mozilla side must less fix it. Firewalls , etc do not cause the leak. You can remove all your ad-ons and leave firefox open and it will suck memory. Every tab you open drains your memory and continues to climb without opening any more. You can then close all your tabs and Firefox will not release the memory. Just fix it guys, it cant be that difficult "
    Posteby Onmicide at https://support.mozilla.org/en-US/questions/939920
    "There is a way to stay on top of the memory usage:
    Go to about:memory and scroll to the bottom. There are buttons there for garbage collection and minimizing memory usage. "

    Please try this two minute test.
    '''Create a new Firefox profile'''
    A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also should have completely fresh settings databases and a fresh cache folder.
    Exit Firefox and start up in the Profile Manager using Start > search box (or Run):
    firefox.exe -P
    Any time you want to switch profiles, exit Firefox and return to this dialog.
    You'll click the Create Profile button. I recommend using the default location suggested, and to avoid data loss, not re-using any existing folder. Then start Firefox in the new profile you created.
    What happens with memory usage with the two default tabs open, or another tab of your choice?
    When returning to the Profile Manager, you might be tempted to use the Delete Profile button. But... it's a bit too easy to accidentally delete your "real" profile, so I recommend resisting the temptation. If you do want to clean up later, I suggest making a backup of all your profiles first in case something were to go wrong.

  • [LPX] Drummer/Drum Kit Designer memory leak causing crash

    After working with LPX for a couple of days after release with almost no problems save for a few system overload errors that always seemed to sort themselves out, I loaded up a project I had been working on to find that it crashed every time I tried to play the track. Other, smaller projects, still played in varying degrees, some having to wait for a long time seemingly for samplers to load up etc.
    I did some testing (painstaking, considering that I was having to force-quit the application for my computer to even run again; as an aside there were never any error reports for whatever reason) and found that it appears to be Drummer/Drum Kit Designer that's causing massive memory usage. Looking at the activity monitor when loading the project revealed that the memory usage would just go up and up until it maxed out my (rather modest) 4GB RAM, at which point there would be no free memory and the computer would slow almost to a standstill. Removing all instances of Drum Kit Designer and Drummer reduces the load to a point where it is once again manageable.
    This seems like a fault in Drummer, I'm thinking possibly a memory leak. Has anyone else been experiencing this problem/anyone have any thoughts as to how it could be fixed?
    Thanks in advance,
    Jasper

    This is not a memory bug. It's simply the nature of the new Drummer.
    Drummer uses a LOT of samples. It's a 13GB download for a reason. You will need more than 4GB to use drummer and not run into issues.
    The nature of the modern Logic engine - which seems unchanged from v9 - makes it very bad at being able to tell when it's running out of memory. Logic will simply freeze or crash most of the time it runs out. The freeze would be down to it using literally every last MB on your RAM without overstepping the boundary, and the crash would be downt to it claiming to need more real RAM than you have spare.
    Producer kits use 5.1 surround samples, and submixes them to stereo in a way that posistions them around the space. Whilst a doddle for a modern machine, you Mac is rather long in the tooth to be trying to do that whilst struggling to handle 1.2GB patches with 4GB of RAM total.

  • New memory leak with CS4 update?

    I just downloaded the CS4 update last night, and was doing my normal photoshop work when I had to re-start the application due to what looks like a memory leak.
    Windows XP, 3GHZ dual core ( 45 nm one ), 4 GB RAM, NVidia 9600 GT, no GPU enabled ( still comes up with that error even with newest drivers ).
    128MB TIFF file was my source.
    I had 3 layers, then copy merged all to another layer so I could liquify.
    Liquify was getting REALLY sluggish when trying to zoom, but was usable.
    After 10 minutes here, I clicked "ok" to return the results, then it said there wasn't enough memory to do it. So I had to cancel. Process was using right around 2 GB. I saved my PSD file ( around 256 MB ) and closed it. CS4 was still using around 2 GB with no documents open. So I closed CS4 and I had multiple errors pop up saying couldn't export or copy from clipboard because not enough memory.
    Brought CS4 back up and loaded in that 256MB psd file, everything was fine.

    I've been told by support that I need to un-install CS4, and re-install it and the patch in order to rectify my problem. The cause of the problem they are saying is a failed application of the patch.
    Is this a bunch of BS to keep me busy for a while? How do I know that the next time everything will install correctly?
    This will take some time to do, and I'll have to figure out how to backup all my settings/scripts.

  • I think I've got a memory leak and could use some advice

    We've got ourselves a sick server/application and I'd like to gather a little community advice if I may. I believe the evidence supports a memory leak in my application somewhere and would love to hear a second opinion and/or suggestions.
    The issue has been that used memory (as seen by FusionReactor) will climb up to about 90%+ and then the service will start to queue requests and eventually stop processing them all together. A service restart will bring everything back up again and it could run for 2 days or 2 hours before the issue repeats itself. Due to the inconsistant up time, I can't be sure that it's not some trouble bit of code that runs only occasionally or if it's something that's a core part of the application. My current plan is to review the heap graph on the "sick" server and look for sudden jumps in memory usage then review the IIS logs for requests at those times to try and establish a pattern. If anyone has some better suggestions though, I'm all ears! The following are some facts about this situation that may be usefull.
    The "sick" server:
    - CF 9.0.1.274733 Standard
    - FusionReactor 4.0.9
    - Win2k8 Web R2 (IIS7.5)
    - Dual Xeon 2.8GHz CPUs
    - 4GB RAM
    JVM Config (same on "sick" and "good" servers):
    - Initial and Max heap: 1536
    -server -Xss10m -Dsun.io.useCanonCaches=false -XX:PermSize=192m  -XX:MaxPermSize=256m -XX:+UseParNewGC -Xincgc -Xbatch -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib -Dcoldfusion.dotnet.disableautoconversion=true
    What I believe a "healthy" server graph should look like (from "good" server):
    And the "sick" server graph looks like this:

    @AmericanWebDesign, I would concur with BKBK (in his subsequent reply) that a more reasonable explanation for what you’re seeing (in the growth of heap) is something using and holding memory, which is not unusual for the shared variables scopes: session, application, and/or server. And the most common is sessions.
    If that’s enough to get you going, great. But I suspect most people need a little more info. If this matter were easy and straightforward, it could be solved in a tweet, but it’s not, so it can’t.
    Following are some more thoughts, addressing some of your concerns and hopefully pointing you in some new directions to find resolution. (I help people do it all the time, so the good news is that it can be done, and answers are out there for you.)
    Tracking Session Counts
    First, as for the observation we’re making about the potential impact of sessions, you may be inclined to say “but I don’t put that much in the session scope”. The real question to start with, though, is “how many sessions do you have”, especially when memory use is high like that (which may be different than how many you have right now). I’ve helped many people solve such problems when we found they had tens or hundreds of thousands of sessions.  How can you tell?
    a) Well, if you were on CF Enterprise, you could look at the Server Monitor. But since you’re not, you have a couple of choices.
    b) First, any CF shop could use a free tool called ServerStats, from Mark Lynch, which uses the undocumented servicefactory objects in CF to report a count of sessions, overall and per application, within an instance. Get it here: http://www.learnosity.com/techblog/index.cfm/2006/11/9/Hacking-CFMX--pulling-it-all-togeth er-serverStats . You just drop the files (within the zip) into a web-accessible directory and run the one CFM page to get the answer instantly.
    c) Since you mention using FusionReactor 4.0.9, here’s another option: those using FR 4 (or 4.5, a free update for you since you’re on FR 4) can use its available (but separately installed) FusionReactor Extensions for CF, a free plugin (for FR, at http://www.fusion-reactor.com/fr/plugins/frec.cfm). It causes FR to grab that session count (among many other really useful things about CF) to log it every 5 seconds, which can be amazingly helpful. And yes, FREC can grab that info whether one is on CF Standard or Enterprise.
    And let’s say you find you do have tens of thousands of sessions (or more). You may wonder, “how does that happen?“ The most common explanation is spiders and bots hitting your site (from legit or unexpected search engines and others). Some of these visit your site perhaps daily to gather up the content of all the pages of your site, crawling through every page. Each such page hit will create a new session. For more on why and how (and some mitigation), see:
    http://www.carehart.org/blog/client/index.cfm/2006/10/4/bots_and_spiders_and_poor_CF_perfo rmance
    About “high memory”
    All that said, I’d not necessarily conclude so readily that your “bad” memory graph is “bad”. It could just be “different”.
    Indeed, you say you plan to “look for sudden jumps in memory usage“, but if you look at your “bad” graph, it simply builds very slowly. I’d think this supports the notion that BKBK and I are asserting: that this is not some one request that “goes crazy” and uses lots of memory, but instead is the “death by a thousand cuts” as memory use builds slowly.  Even then, I’d not jump at a concern that “memory was high”.
    What really matters, when memory is “high” is whether you (or the JVM) can do a GC (garbage collection) to recover some (or perhaps much) of that “high, used memory”. Because it’s possible that while it “was” in use in the past (as the graph shows), it might no longer be “in use” at the moment . 
    Since you have FR, you can use its “System Metrics page” to do a GC, using the trash can in the top left corner of the top right-most memory graph. (Those with the CFSM can do a GC on its “Memory Usage Summary” page, and SeeFusion users can do it on its front page.)
    If you do a GC, and memory drops q lot, then you had memory that “had been” but no longer ”still was” in use, and so the high memory shown was not a problem. And the JVM can sometimes be lazy (because it’s busy) about getting to doing a GC, so this is not that unusual. (That said, I see you have added the Xincgc arg to your JVM. Do you realize that tells the JVM not to do incremental GCs? Do you really want that? I understand that people trade jvm args like baseball cards, trying to solve problems for each other, but I’d argue that’s not the place to start. In fact, rarely do I find myself that any new JVM args are needed to solve most problems.)
    (Speaking of which, why did you set the – xss value? And do you know if you were raising or lowering it form the default?)
    Are you really getting “outofmemory” errors?
    But certainly, if you do hit a problem where (as you say) you find requests hanging, etc., then you will want to get to the bottom of that. And if indeed you are getting “outofmemory” problems, you need to solve those. To confirm if that’s the case, you’ll really want to look at the CF logs (specifically the console or “out” logs). For more on finding those logs, as well as a general discussion of memory issues  (understanding/resolving them), see:
    http://www.carehart.org/blog/client/index.cfm/2010/11/3/when_memory_problems_arent_what_th ey_seem_part_1
    This is the first of a planned series of blog entries (which I’ve not yet finished) on memory issues which you may find additionally helpful.
    But I’ll note that you could have other explanations for “hanging requests” which may not necessarily be related to memory.
    Are you really getting “queued” requests?
    You also say that “the service will start to queue requests and eventually stop processing them all together”. I’m curious: do you really mean “queuing”, in the sense of watching something in CF that tells you that? You can find a count of queued requests, with tools like CFSTAT, jrun metrics, the CF Server Monitor, or again FREC. Are you seeing one of those? Or do you just mean that you find that requests no longer run?
    I address matters related to requests hanging and some ways to address them in another entries:
    http://www.carehart.org/blog/client/index.cfm/2010/10/15/Lies_damned_lies_and_CF_timeouts
    http://www.carehart.org/blog/client/index.cfm/2009/6/24/easier_thread_dumps
    Other server differences
    You presented us a discussion of two servers, but you’ve left us in the dark on potential differences between them. First, you showed the specs for the “sick” server, but not the “good” one. Should we assume perhaps you mean that they are identical, like you said the JVM.config is?
    Also, is there any difference in the pattern of traffic (and/or the sites themselves) on the two servers? If they differ, then that could be where the explanation lies. Perhaps the sites on one are more inclined to be visited often by search engine spiders and bots (if they sites are more popular or just have become well known to search engines). There are still other potential differences that could explain things, but these are all enough to hopefully get you started.
    I do hope that this is helpful. I know it’s a lot to take in. Again, if it was easier to understand and explain, there wouldn’t be so much confusion. I do realize that many don’t like to read long emails (let alone write them), which only exacerbates the problem. Since all I do each day is help people resolve such problems (as an independent consultant, more at carehart.org/consulting), I like to share this info when I can (and when I have time to elaborate like this), especially when I think it may help someone facing these (very common) challenges.
    Let us know if it helps or raises more questions. :-)
    /charlie

  • Memory leak in Safari 4 & 5

    In 10.5 and 10.6, Safari has what I think is called a memory leak. It ties up memory that it is not actually using, so that its use balloons. I can quit and re-open all the same windows and gain half a gig of memory back.
    Anybody know a way to stop this?

    There is an on-going thread from Aug 2009 about "Snow Leopard" and "Memory Leak" or similarly "Memory Hog" etc and not releasing memory as well as how Safari is one of the worst offenders for many others.
    Some have 4GB RAM and no trouble, some with same amount but do.
    And of course clearing Previews, History, Cache, even the Bookmarks cache.
    ~/Library/Caches/
    Flash and other plug-ins, (flash has its own cache) and using something to only load Flash if desired.
    But most found 10.5 and Safari 4 "better behaved" and not the issue 5.0 and 10.6 are.

Maybe you are looking for