Lightroom CC 2015.5 - memory leak?

I reinstalled my computer just after doing a few hardware upgrades (12 GB - > 16GB, 500GB SSD, new video card) and now if Lightroom works for about 30-40 minutes, Windows warns me that my system is out of memory.

I restarted Lightroom and opens the window information system and watched the real and the virtual memory used by Lightroom values just start a slow climb while the program was not yet in use.

I've seen similar posts on Lr and a memory leak, but not quite the same circumstances.

I am including the full screen Sys Info then that a few cases a minute apart on two counters memory below.  Any suggestion would be appreciated.  The creative cloud app said that I have the current version.

Version of Lightroom: CC 2015.5 [1067055]

License: Creative Cloud

Operating system: Windows 7

Version: 6.1

Application architecture: x 64

System architecture: x 64

Number of logical processors: 8

Processor speed: 3.3 GHz

Built-in memory: 16366,4 MB

Real memory for Lightroom: 16366,4 MB

Real memory used by Lightroom: 1063,8 Mo (6.4%)

Virtual memory used by Lightroom: 1060,0 MB

Memory cache size: 572,7 MB

Maximum thread count used by Camera Raw: 8

Camera Raw SIMD optimization: SSE2, AVX

System DPI setting: 96 DPI

Composition of the Bureau enabled: Yes

Exhibition: 1) 1920 x 1080, 2) 1920 x 1080, 3) 1920 x 1080, 4) 1920 x 1080

Entry types: Multitouch: no, built-in touch: No, built-in pen: no, touch external: No, external pen: no keyboard: No.

News of GPU: GeForce GTX 950/PCIe/SSE2

Check the supported OpenGL: past

Provider: NVIDIA Corporation

Version: 3.3.0 NVIDIA 364.72

Rendering engine: GeForce GTX 950/PCIe/SSE2

LanguageVersion: 3,30 NVIDIA via the Cg compiler

The application folder: C:\Program Files\Adobe\Adobe Lightroom

Library path: D:\Miscellaneous\Lightroom\Lightroom Catalog.lrcat

Settings folder: C:\Users\Administrator\AppData\Roaming\Adobe\Lightroom

Plugins installed:

(1) home canon Plugin

(2) Facebook

(3) Flickr

(4) HDR Efex Pro 2

(5) attachment Plugin Leica

(6) home Plugin Nikon

(7) SmugMug

Config.LUA flags: None

Map #1: Seller: 10de

Feature: 1402

Subsystem: 32081462

Revision: a1

Video memory: 1969

AudioDeviceIOBlockSize: 1024

AudioDeviceName: Pregnant (2-High Definition Audio Device)

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 44100

Build: LR5x102

Direct2DEnabled: false

GPUDevice: not available

OGLEnabled: true


Real memory used by Lightroom: 1063,8 Mo (6.4%)

Virtual memory used by Lightroom: 1060,0 MB

Real memory used by Lightroom: 1615,9 MB (9.8%)

Virtual memory used by Lightroom: 1731,9 MB

Real memory used by Lightroom: 1737,3 MB (10.6%)

Virtual memory used by Lightroom: 1882,7 MB

Real memory used by Lightroom: 1999,6 MB (12.2%)

Virtual memory used by Lightroom: 2204,4 MB


Thank you


I suggest rolling back to LR CC 2015.4 as described here:

Roll of Lightroom version prior update

Change step 3 on the link above to read:

(3) download and install the 2015.5 / 6.5 release

Try again with LR CC 2015.4

Tags: Photoshop Lightroom

Similar Questions

  • CC 2015.4 memory leak

    For some reason, my project was fine before the update of 2015.3 to 2015.4. Now my memory fills up, on the same project and finally hangs after 5-10 minutes in there. I have 32 GB and have never had this problem, even on much larger projects.

    I have a solution for those who have problems of memory when opening projects more important that have been created in versions earlier and migrated to 2015.4.

    I had this problem too with a long doc project (big enough) and figured out the problem occurs when the first is simultaneously trying to load a large number (thousands) of the components in the project files * and * simultaneously creating pic/media file cache.

    So the trick is to force to tackle these things separately - so I developed this work around. Not sure if all these steps are necessary, but it worked for me.

    First of all, go to preferences-> memory and make sure that you allocate a decent piece to other applications. About 1/4 of your total physical RAM. Then change the "optimize rendering for" menu drop-down 'performance' to 'memory' - then get out, reboot first to make sure that this setting of the sticks. Also useful to make sure that your swap file is also great that you can get away with. With modern hard disks, you should easily have 20 or 40 GB you can make of it.

    Create a new project file and begin to import all your belongings into small pieces. In my project, that the assets were in folders according to the day of shooting, so I brought in each folder of day of filming separately through the media browser.

    What happens is that the number of files is relatively small, so first get through those loading fast enough, so he is not at the same time loading and cached for an extended period.

    With each batch that bring you, let him finish caching all files before importing the next batch. A lot of time Yes, but if you keep your Windows resource monitor (or whatever the equivalent of Mac is) you will notice that the amount of memory used is the level specified in the Preferences dialog box of memory in mind.

    Once you have imported all your belongings back, use the media browser to access your old project file and bring your old sequences in the new project. Assuming that all the media is where the old project thought that they were, first should not try to re-import all media, but rather to use the media that you have already imported and match it to the top.

    NB of Adobe - this workaround is a ballache and I'm * really * not impressed as a user of creating some 17 years that I have to go through these hoops just to open a project. He meets. Seriously. Resolve is looking pretty attractive right now.

  • Premiere Pro CC 2015 memory leak

    Did the upgrade for 2015 of CC.

    I got my iMac freezes several times with the warning of 'Out of Memory' and the body is the culprit using massive amounts.  Currently I'm looking at him, sitting idle with a project relatively small (23 min series episode, 827KB project file) and the memory usage is increased from 2GB about to 35 GB (25,19 GB compressed memory).

    I did the upgrade on my mac backup. I have just wrapped real concerts and have time to test the new version during some downtime.  Then... I have about 3 weeks to figure things before customers receive in return.  I'm a big fan of the integration of Lumetri.  It is the largest most for my workflow and I want to use it with customer projects based, but the system must be running smooth.  And the question of memory is the opposite of the smooth.

    I optimized my settings memory for use only 26 GB Agency (which I guess it does if you go through the memory compressed using sound).  "Scratch disks" is set to 'same as project... '. "which lie off the coast of the main HD.

    I tried the trick to disable auto save function (which is the worst thing to... use autosave will save real madness).  Turn it off did nothing to relieve the memory leak, so it's back as it should.

    iMac (retina, 5K, end of 2014)

    4 GHz Intel Core i7

    32 GB 1600 MHz DDR3

    AMD Radeon R9 M295X 4096 MB

    Ventilation full memory usage because it is currently:

    Screen Shot 2015-06-26 at 10.02.19 AM.png

    I've updated my blackmagic drivers.

    I see that Adobe QT32 server constantly sitting as "Not responding" and there is always at least 2 instances of run (which confuses me).

    I don't know if more info is needed.

    Any suggestions?

    Hi Rio,

    Thanks for the suggestions... However as an update on my situation.  I updated my OS as bsbeamer pointed out.  After a good 10 hours of use it yesterday, keep it open all night... I stayed in the range of 3 to 9 GB of memory used.  So things seem to have settled down.

    I did not change the allocation of memory, just the OS update.

    See you soon

  • My Macbook Pro reboots after a memory leak every two hours

    Hey everybody. I'm having a problem with my MacBook Pro (retina, mid-2012), where he is recovering in market (usually after gel). In this case only (so far) while using Adobe Illustrator CC 2015 (to date). I also use a Wacom tablet (intuos 4, with latest drivers), drawing, which can also be the culprit.

    This happened with Yosemite, so I had upgraded to El Capitan - that does not solve the problem.

    I apologize if the problem is with myself! I get that this problem is probably the fault of Wacom, Adobe or myself - I just want to see what you think Mac-heads.

    Thanks a lot, a lot in advance for any advice - I appreciate any help I can get.

    The report I get, when restarting is as follows:

    Mon 4 Jan 20:19:13 2016

    Panic report *.

    panic (the appellant UC 7 0xffffff802d928e44): "zalloc: map of exhausted area during the allocation of the buf.8192 area, probably because of the memory leak in the area kalloc.512 (1063772160 bytes, 2076706 elements allocated)"@/Library/Caches/ /zalloc.c:2543.

    Backtrace (CPU 7), Frame: Return address

    0xffffff813887b150: 0xffffff802d8e5357

    0xffffff813887b1d0: 0xffffff802d928e44

    0xffffff813887b300: 0xffffff802daea851

    0xffffff813887b330: 0xffffff802dae8f19

    0xffffff813887b380: 0xffffff802dae8a23

    0xffffff813887b450: 0xffffff802daea040

    0xffffff813887b4b0: 0xffffff802dcf76fb

    0xffffff813887b520: 0xffffff802dd4cdfb

    0xffffff813887b5c0: 0xffffff802dd47845

    0xffffff813887b6d0: 0xffffff802dcfe66b

    0xffffff813887bc10: 0xffffff802dd3e695

    0xffffff813887bd20: 0xffffff802db112f2

    0xffffff813887bde0: 0xffffff802db1ce7c

    0xffffff813887bf30: 0xffffff802db11747

    0xffffff813887bf60: 0xffffff802de2ace1

    0xffffff813887bfb0: 0xffffff802d9f4896

    The process corresponding to the current thread BSD name: softwareupdated

    Mac OS version:

    15A 284

    Kernel version:

    Darwin Kernel Version 15.0.0: Wed Sep 26 16:57:32 PDT 2015; root:XNU-3247.1.106~1/RELEASE_X86_64

    Kernel UUID: 37BC582F-8BF4-3F65-AFBB-ECF792060C68

    Slide kernel: 0x000000002d600000

    Text of core base: 0xffffff802d800000

    Text __HIB base: 0xffffff802d700000

    Name of system model: MacBookPro10, 1 (Mac-C3EC7CD22292981F)

    Availability of the system in nanoseconds: 7390442512484

    Area name heart size free size

    VM 146329200 960 items

    machine virtual object hash 24008000 2240 c'entri

    VM 46592000 883520 map entries

    34959024 5424 pv_list

    VM 130327232 8768 pages

    16598128 27424 Kalloc.16

    16876000 21664 Kalloc.32

    77735808 199344 Kalloc.48

    Kalloc.64 37787264 95360

    2136000 5280 Kalloc.80

    Kalloc.96 1729824 67200

    Kalloc.128 130555904 30464

    1941600 135680 Kalloc.160

    133074944 292352 Kalloc.256

    45504 142195392 Kalloc.288

    1063772160 498688 Kalloc.512

    1003634688 2931712 Kalloc.1024

    6909952 24576 Kalloc.2048

    Kalloc.4096 9760768 0

    Kalloc.8192 10452992 0

    9606272-3968 mem_obj_control

    SCHED groups 1270080 36288

    IPC 81922240 150880 ports

    2081376 274480 discussions

    x 86 fpsave State 1411072 233792

    uthreads 1224752 209264

    31705680 2640 nodes

    12949920 4032 namecache

    Node 42278544 72816 HFS

    Fork 8548352 896 HFS

    1109304 1176 decmpfs_cnode

    buf.8192 23584768 0

    ubc_info area 5679696 6600

    vnode pager 2580000 1320 structur

    34320384 44864 compressor_pager

    20094976 5986304 compressor_segment

    The 3653632 kernel stacks

    PageTables 250183680

    Kalloc.Large 166412827

    Backtrace suspected leakage: (bytes pending: 206848)














    Extensions of core in backtrace: (203.7.1) [5178DF8C-1F96-3D 87-8BD4-46B996C41 84A]@0xffffff7fafd4e000-> 0xffffff7fafdb9fff

    dependency: (2.9) [668E3DEE-F98E-3456-92D6-F4FEEA355A72] @ 7fae12d000 0xffffff

    dependency: (2.4.1) [48AC8EA9-BD3C-3FDC-908D-09850215AA32] @0 xffffff7fae4a2000 (10.0.6) [7246A48B-E43B-3AF3-8285-8E793AE55B8C] @0xffffff7fafdc8 000-> 0xffffff7fafe64fff

    dependency: (2.9) [668E3DEE-F98E-3456-92D6-F4FEEA355A72] @ 7fae12d000 0xffffff

    dependency: ffff7fae4e9000 @0xff (2.4.1) [814A7F4B-03EF-384A-B205-9840F0594421]

    dependency: (10.0.6) [E177026A-B6F5-30AB-BF87-8ADC4D102278] @0xffffff7fae4ff000

    dependency: (2.4.1) [48AC8EA9-BD3C-3FDC-908D-09850215AA32] @0 xffffff7fae4a2000

    dependency: (203.7.1) [5178DF8C-1F96-3D 87-8BD4-46B996C41 84A]@0xffffff7fafd4e000

    last load kext to 510536257340: 3 (addr 0xffffff7fb0a11000 size 32768)

    Finally unloaded kext to 584400762104: 3 (addr 0xffffff7fb0a11000 size 32768)

    kexts responsible: 1.70 1.9.5d0 110.20.19 2.5.1d0 1.0.0

    com Apple.filesystems.autofs 3.0 124 1 272.50

    com Apple.Driver.pmtelemetry 1 272.50 1.0.1 4.4.0f4 3.6.1 7.0.0 10.0.8 10.0.6 1 4.4.0f4 1.0.0 3.0.8 3.1 208 1.2.13 10.0.8 3.11.31 4.0.0 245,4 245,4 1.0.0d1 1.0.0 37 2.8.0 1.7.0 1000.13.1a3 1.0.1

    3.1.5 4.0 161.0.0 2.0 1.8 2.1 4.0 1.7 218.0.0

    com Apple.NKE.applicationfirewall 163

    com Apple.Security.Quarantine 3 8 218.0.0 181 4.4.0f4 181

    com Apple.kext.Triggers 1.0 272.50 525 11 108.0.1 10.0.6 10.0.6 1 4.4.0f4 4.4.0f4 272.50 272.50 203.8 1.2.0 1.0.14d1 1.0.14d1 203.7.1 3.11.31 1.1.0 2.4.1 3.11.31 2.4.1 1.0.0 3.1.9 6.0.0d7 1.0.0 3.7.7 250.4 900.4.1 1.0.1 1.0.1 517 4.1.2 4.1.2 2.0.2 4.0.1 5.0.6 1100.23 1.0.1b8 3.2

    com Apple.Driver.corecapture 1.0.4 1.0.1 2.8.0 1.0.1 1.0.1 900.4.1 1.0.1 1.0.1 2.0 2.0.0 2.0 1.1

    com Apple.Security.sandbox 300.0 1.0.0d1 2 1.0.5 1.0 414 2.1 31 28.30 4.0 2.9 1.4 1

    com Apple.KEC.pthread 1

    com Apple.KEC.corecrypto 1.0

    Panic report suggests that the issue is in the video/graphis material. Please make an appointment at the Apple Store - Genius Bar store and bring it into service. If you are in the United States or is unable to make an appointment in this way, contact your Apple store.

  • Release of Lightroom CC 2015.6 VERY SLOW!

    Hi guys,.

    I use Lightroom CC 2015.6 contacted Camera RAW 9.6 out of 10 Pro 64 bit and I have pretty decent rig: i7 6950 X (10 carrots), Asus Radeon Strix 1080 GTX, 64 GB 3200 RAM, SSD on PCI.  'Use the graphics processor' is enabled in my preferences of LR, but I don't see an important when different it is turned off.

    First of all it takes LR about 3-4 seconds per image to build 1:1 previews, which means several hours if I have thousands of images from a shoot.

    When I try to get a glimpse of some of the images at 100%, and to quickly move between them it works fine for maybe 5 minutes and then it starts to slow down: it takes LR seconds to create each preview and also from seconds to move between images. Furthermore, the previews are 3840px in size and average quality.

    In Manager tasks I can see that at the start after start LR uses only 5-10% of my CPU resources and about 2 to 5 GB of RAM, but after a few minutes the use of RAM increases 15-20 GB and that's when LR becomes very slow. It seems he keeps each image previewed in memory and not release to the system when I close the preview.

    I also tried another software to compare and other programs were significantly faster (Aftershot Pro is the fastest, followed by DXO Optics Pro and Capture One).

    So it seems that this problem is strictly linked to the software and not to my material at all. Also, I noticed that after the recent updates, so I wonder if relling until one of the earlier versions might help.

    Ideas to improve my experience with the latest edition of LR?

    I'm really scared, because I don't really have time to wait for the software when working on thousands of images each week.

    Your response will be appreciated. Thank you!

    This is the official Adobe performance help page.
    Adobe Lightroom GPU troubleshooting and FAQ

    You have your system configured to save all 1:1 previews in your catalog for ever? I set mine to delete every 30 days, so I don't have all that stored somewhere in a cache with LR.

    Because it goes so slow down anyway I don't think you have much to lose by trying to clear your cache. But read up on it before making this decision.

    In addition, if your photos are stored on an external I wonder if there is a problem with this external hard drive bus speed?

    Or if it's all beings stored on your local disk with the OS and applications, maybe it's having a shape any conflict with something the OS or a partner app? Do you think these performance issues when other applications are turned off? Just think-tanking with you here because it seems to have no else responded yet.
    Hope of those is the solution.


  • Lightroom CC 2015.3 keep craching whenever I try to import images

    Hi, could someone help me please. Lightroom CC 2015.3 crashes whenever I try to import images. Operating system iMac OSX EL Capitan 10.11.2 retina 4 k, 21.5 inches, end of 2015, 3.1 GHz processor intel core i5, memory 8 GB 1867 mhz ddr3 graphics card intel graphics pro 6200 1536 MB. Thanks for any help!

    Hi Antonio,.

    I suggest you first Lightroom update for the latest version of Lightroom 2015.4: keeping up-to-date for Lightroom

    Once that is done, then please go ahead and try to import images into Lightroom.

    Let me know if the app crashes yet or not.

    Kind regards


  • GPU acceleration does not work in Lightroom CC 2015.3

    Can someone help me why Lightroom cannot use GPU acceleration? In Preferences > performance, if I check 'Use Graphics Processor', he says "GPU acceleration has been disabled due to errors.". In system information, it does not show the graphics card information:

    Version of Lightroom: CC 2015.3 [1052427]

    License: Creative Cloud

    Operating system: Mac OS 10

    Version: 10.11 [1]

    Application architecture: x 64

    Number of logical processors: 8

    Processor speed: 3.5 GHz

    Built-in memory: 16 384.0 MB

    Real memory for Lightroom: 384.0 MB 16

    Real memory used by Lightroom: 1 368,1 MB (8.3%)

    Virtual memory used by Lightroom: 2 889,8 MB

    Memory cache size: 451,1 MB

    Maximum thread count used by Camera Raw: 8

    Camera Raw SIMD optimization: SSE2, AVX

    Exhibition: 1) 2560 x 1600

    Graphic processor News:

    Check the supported OpenGL: failed



    Rendering engine:


    In photoshop, it works correctly as it appears as a disorder in lightroom.

    System information from Photoshop:

    Adobe Photoshop Version: 20151114.r.301 2015.1 2015/11 / 14:23:59:59 CL 1053036 x 64

    Operating system: Mac OS 10.11.1

    System architecture: Intel CPU Family: 6, model: 42, Stepping: 7 with MMX, SSE whole, FP SSE, SSE2, SSE3, SSE4.1, SSE4.2, AVX, HyperThreading

    Physical processor count: 4

    Number of logical processors: 8

    Processor speed: 3503 MHz

    Built-in memory: 16384 MB

    Free memory: 9953 MB

    Memory available to Photoshop: 14720 MB

    Memory used by Photoshop: 70%

    Range of modifier: disabled.

    Space design: enabled.

    Work plans: enabled.

    Multi-frequency 3D printing: disabled.

    HighBeam: enabled.

    Tile image size: 1024K

    Image cache level: 4

    Overview of fonts: medium

    TextComposer: Latin

    Display: 1

    Main screen

    Limits of the display: top = 0, left = 0, low = 1600, right = 2560

    OpenGL drawing: enabled.

    OpenGL allows old GPU: not detected.

    OpenGL drawing mode: Advanced

    OpenGL allows Normal Mode: true.

    OpenGL allows Advanced Mode: true.

    AIFCoreInitialized = 1

    AIFOGLInitialized = 1

    OGLContextCreated = 1

    NumGLGPUs = 1

    NumCLGPUs = 1

    glgpu [0]. GLVersion = "2.1".

    glgpu [0]. IsIntegratedGLGPU = 0

    glgpu [0]. GLMemoryMB = 2048

    glgpu [0]. GLName = "NVIDIA GeForce GTX 960 engine OpenGL"

    glgpu [0]. GLVendor = "NVIDIA Corporation".

    glgpu [0]. GLVendorID = 4318

    glgpu [0]. GLRectTextureSize = 16384

    glgpu [0]. GLRenderer = "NVIDIA GeForce GTX 960 engine OpenGL"

    glgpu [0]. GLRendererID = 16918374

    glgpu [0]. HasGLNPOTSupport = 1

    glgpu [0]. CanCompileProgramGLSL = 1

    glgpu [0]. GLFrameBufferOK = 1

    glgpu [0] .glGetString [GL_SHADING_LANGUAGE_VERSION] = '1.20 '.


    glgpu [0] .glGetIntegerv [GL_MAX_TEXTURE_UNITS] = [8]

    glgpu [0] .glGetIntegerv [GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS] = [16]

    glgpu [0] .glGetIntegerv [GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS] = [16]

    glgpu [0] .glGetIntegerv [GL_MAX_TEXTURE_IMAGE_UNITS] = [16]

    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] = [4096]

    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.2 (September 21, 2015 19:24:11)" "

    clgpu [0]. CLDeviceVersion = "1.2".

    clgpu [0]. IsIntegratedCLGPU = 0

    clgpu [0]. CLMemoryMB = 2048

    clgpu [0]. CLName = 'GeForce GTX 960.

    clgpu [0]. CLVendor = "NVIDIA".

    clgpu [0]. CLVendorID = 16918272

    clgpu [0]. CLDriverVersion = "" 10.7.47 346.03.03f02 ""

    clgpu [0]. CUDASupported = 0

    clgpu [0]. CLBandwidth = 8.20418e + 10

    clgpu [0]. CLCompute = 632.388

    Type of license: subscription

    Serial number: 96040921540346380076

    Feature::Photoshop / Extended: WE

    Feature::Photoshop/standard: WE

    Feature::Photoshop/test: OFF

    Feature:32 - Bit layers: WE

    Feature::CountTool: WE

    Feature::Acrobat3D: WE

    Feature::measurement: WE

    Feature::MATLAB: WE

    Feature::VanishingPointMeasurement: WE

    Feature::VanishingPoint3DSExport: WE

    Feature::VanishingPointDXFExport: WE

    Feature::DICOM: WE

    Feature::VideoLayers: WE

    Feature::Timeline: WE

    Feature::ExtendedMenuBar: WE

    Feature::3DPrint App: WE

    Feature::ImageStack creation: WE

    Feature::ImageStack edition: WE

    Feature:32 - Bit painting: WE

    Feature::ACRFilterAllowed: WE

    Feature::ACRFilterAvailable: WE

    Feature::ExportAssetsQueueFeature: OFF

    Feature::creative cloud staged: OFF

    Feature::3DMultitonePrinting: OFF

    Feature::artboards: WE

    Feature::Playground: WE

    Palette Feature::chording: OFF

    Application folder: Applications/Adobe Photoshop CC 2015.

    Zero Photoshop has async I/O active

    Scratch the volumes:

    1.14 T, 734,2 G free starter

    Required plugins folder: / Applications / Adobe Photoshop 2015/Adobe Photoshop CC CC

    Main Plug-ins folder: / Applications / Adobe Photoshop CC 2015/plugins /.

    It should work. I'm not very familiar with Mac. Make sure you are using the latest driver available for the card and reset the driver to their default settings.

  • Since the upgrade to Sierra MediaLibraryService is causing a memory leak


    I upgraded to Sierra, since as soon as Itunes is launched, the is originally a large memory leak, it keeps in ram more until she takes all (16 GB) and significantly slows down the computer.

    I tried to reset the nvram and smc memory, doesn't change anything.

    Does anyone have an idea on what is causing this leak and is there a solution?

    Yes, I noticed this also. After that I opened iTunes, it's just a matter of time before all the memory gets used up and all departure is wobbly. In particular, bluetooth really gets bug after a certain time, and as soon as I quit iTunes, that's fine.

  • There seems to be a MAJOR problem (blocking/memory leak) in "subject: House", also known as the Firefox Start Page, at 26.0 Firefox on Windows!

    There seems to be a MAJOR problem (blocking/memory leak) in "subject: House", also known as start up Firefox, 26.0 Firefox Page, Windows!

    seen on:
    -Windows 7 x 64 machine with 12 GB of RAM and high performance CPU (core i7-920)
    -Comments Machine virtual WinXP SP3 (in Oracle VirtualBox) running on the same computer
    -Intel Atom D525 netbook with 4 GB of RAM, running Win7 x 64

    None of these machines are connected through Sync or something like that. The Firefox instance on the virtual machine is a fresh install / clean.

    The problem:
    -100% of cpu usage for 10 seconds, (util in XP) memory usage goes up to 1.7 GB
    -If "subject: House" is actually the Firefox Start Page, it blocks the computer at startup of Firefox for 10 seconds
    -If "subject: House" isn't the Firefox Start Page, startup is fine - BUT if I press the "home" on the toolbar button it loads "on: House" which causes the same question once again

    Sounds that there is a problem with one of the code snippets that are responsible. I've seen several reports on this issue.

    You can set the browser.aboutHomeSnippets.updateUrl pref an empty string on the subject: the page of config to disable loading (new) checked to see if that helps.

    You can open the topic: config page through the address bar

    You must remove the ' storage\moz-security-about + origin "folder in the folder of Firefox to delete already profile stored clips.

    You can use this button to go to the Firefox profile folder:

  • On firefox memory leaks cause blue screens?

    On firefox memory leaks cause blue screens?

    If you encounter blue screen crashes, this majority refers often to an incompatibility with a device driver, especially the graphics drivers. Go to Firefox Safe Mode and disable the use of Firefox hardware acceleration of graphics.

    Assuming that Firefox is closed:

    Hold down the SHIFT key when you start Firefox. You should get a small dialog box. Click on 'Start mode safe' (not reset).

    (If Firefox is running, use Help > restart with disabled modules to call the dialog box.)

    In Firefox, open the Options of the Advanced tab dialog box:

    the button Firefox orange (or the Tools menu) > Options > advanced

    In the mini ' General' tab, uncheck the box for "use hardware acceleration when available.

    This will take effect after you exit Firefox and start it up again (in normal mode).

  • Firefox memory leak <! DIFFICULTY! >

    Hello fellow Firefox users!

    For most of us, Firefox suffers from a memory leak crazy, this can cause slowdown and perhaps even crashes. This happens mainly because when you close the tabs, the RAM, they took is always taxing your computer. Among other things cause this annoying leakage.

    Recently, I switched to Firefox and has this leak. I would not put upward with him, so I put solutions. Here's what I came with.

    Some addons I've handpicked, which when combined, are extremely effective.



    MemoryRestart 1.1

    Firefox slow acting? Try these great modules!

    SpeedFox 0.9.11


    Get all these together and make a leak free and faster Firefox!

    Additional details of the system

       Windows Vista
       Firefox 9.0.1

    More information

    Front of Add-ons
    Firefox could take up to 512 MB and up, leading to problems.
    Firefox could take some time to load the tabs sometimes.
    Download was OK.
    After Add-ons
    Use Firefox NEVER more than 512 MB, typically stays around 300 MB.
    Firefox almost NEVER slows down.
    Downloads go up to 4 x the average speed.
    Computer information
    Windows Vista
    4 GB of ram Ram HQ
    Firefox version 9
    3.0 MHZ AMDPhenII QuadCore
    NIVIDIA, VideoRAM 2048 DDR2

  • Satellite U500 memory leak - 18 p

    I have PSU8CE 18 p Satellite U500 with preinstalled Windows7 Home Premium x 64 with 4 GB RAM. When I start mode safe then memory not sunk. When I start it in Normal mode then nonpaged kernel memory develops up to 3011 MB (~ 4 days running).

    I downloaded poolmon.exe and Crescent pool tag found: "AmlH" (ACPI AMLI Pooltags). In safe mode, this pool has 1 single allocation unit. In Normal Mode ~ every 73 seconds he returned new unit. Size of each unit is 524288 bytes.

    Then I downloaded and installed "Windows Performance Toolkit" and run xperf.exe and xperfview.exe according to

    XperfView watch battery to leak memory in the

    Rootntkrnlmp.exe! KxStartSystemThread/ntkrnlmp.exe! PspSystemThreadStartup/ACPI.sys! ACPIWorkerThread/ACPI.sys! RestartCtxtPassive/ACPI.sys! InsertReadyQueue/ACPI.sys! RunContext/ACPI.sys! ParseTerm/ACPI.sys! Return/ACPI.sys! DupObjData/ACPI.sys! NewObjData/ACPI.sys! HeapAlloc/ACPI.sys! NewHeap/ntkrnlmp.exe! ExAllocatePoolWithTag

    I restored windows to State factory but still present memory leak.

    Memory leaks are a common error in programming.
    leak memory occurs when a computer program consumes memory, but is unable to release it in the operating system.

    In your case, it would be necessary to know what application or process that runs in the background do
    This can be very long process you would need to install a system of fees will need to check the memory leak after each installation of driver or another application

  • Defective touchpad (Synaptics) and slow computer after extended use (memory leak)

    Two problems have been caused with my HP Split 2 x since I bought it 2 months ago:

    (1) the touchpad works sometimes for a few seconds, while the touchscreen still work OK.

    (2) the computer becomes slow after a while of use (which varies from a few minutes to a few hours usually). The Task Manager shows 98%-99% of memory, most of which use (3.6 GB / 4 GB) are not paged memory.

    I suspect the two issues are related to a faulty Synaptics driver, according to:

    and .

    I did the same test as the second link with the same result: Open "Task Manager" (Ctrl-Shift-Esc), on the 'Performance' tab, select 'memory '. Note the value for "Non paged memory. If I move the touchpad, it increases to about 1 MB every 5 seconds. If I stop moving, the value remains constant.

    I use the preinstalled Synaptics driver, version (Sep 06, 2013) for 64-bit 8.1 window.

    Everyone has the same problem, or use it without these issues?

    I would like to know if a restoration system or factory reset may fix.


    Microsoft has just released an update for Synaptics Driver, not thanks to HP which has not found a way to provide the possible Synaptics driver as an OEM update.

    Update Windows Update to Sypatics HD TouchPad two days ago, but I would not be allowed to install as it kept then mainly in giving the 800F0100 error Code. After some research on the Internet I could find that an installation manual after the WU has downloaded the driver would be possible.

    So I went to the Device Manager > mice and other pointing devices > TouchPad Synaptics HID > properties > driver > Update Driver > Browse my computer for driver software and shown the finger/windows/C:\Windows\SoftwareDistribution/Download and everything worked like a charm = D

    I have no more memory leak and now after SEVEN MONTHS I finally can use gestures that it was supposed to.

    But I still annoyed gel problems which in my case is a dysfunction between the screen and the dock.

    Just that you wanted the guys at Microsoft to know is the solution, not the HP that would have had if they have signed and put the driver since November last at our disposal. Blame it on you, HP.


  • UDP/Lakes memory leaks?

    I wonder if anyone has had problems with memory leaks/Lakes when you use UDP and data queues?

    The program has a section of code where the queues are loaded with the data read from different UDP ports. The queues are then read by a loop (which is triggered by a source of synchronization of 1 kHz) and some of the data is displayed on the Panel before the main VI. When the program runs it loses memory about 100 Kbps leading to a failure in about 4-5 hours, when the physical RAM is at its maximum.

    I think that I traced the question (using the DETT it shows several memory allocation operations) to the Subvi I join which fills the queues. Can anyone help to emphasize something that could lead to leaks of memory/Lakes?

    Thank you!

    I suspect that the problem is that you are not emptying queues quickly enough. And is not in the code you have posted. There's also a few subVIs, classes, and controls.

    Usually call loops should only be used on real-time operating systems. They offer no advantage over the standard while loop and have an additional charge when using a desktop OS. Also placing indicators within the quick loops can create problems. The operating system does not update the screen dozens of times per second, so wrote indicators 1000 times per second LV forces or the operating system, or both to manipulate data.

    Having multiple synchronization methods in a loop can lead to problems.  UDP timeout is probably based on the clock count of ticks. If you have the timeout of read of the UPD defined with a value greater than zero, the UDP bed may take longer than the timed loop interval.  The timeout of read UDP allows a wait in a standard while loop.


  • Memory leak with RS-485 visa

    I tried to find a slow memory leak in a large application Labview (2012f3). Using perfmon, probes and breakpoints, I could trace the source of the leak of a series VI communication employing a number of nodes VISA. I have attached a slightly simplified version of the VI leaking (, as well as a VISA vi initialization and a VI of container to test.

    Did anyone see any problems with the serialCommand VI that could possibly cause memory leak?

    After reading all posts of the forum that I could find on memory leaks and VISA error, I was still unable to stop the leak. SomeofthethingsI'vetriedsofar:

    -J' read VISA Close can cause leaks memory, so I disabled inside the loop (even if he was closing an event, not the port)

    -J' wrote extra carriage at the beginning of the VI returns, before rinsing the pads

    -J' was initially using VISA 5.2; After the upgrade to VISA 5.3, the leak occurred still

    -J' replaced VISA nodes with constant value placeholders, and the leak repaired (not a solution, but the confirmation that it is the location of the leak)

    It may also be worth noting that I don't remember when this leak memory in the previous development when I was watching for leaks, but a few days ago Labview executable generates started fails with the error 1, and the only way to get Labview to successfully build again should fix labview from Add/Remove Programs (Win 7 Ultimate) , so it could be related to a change of version in one of the packages that has been reinstalled.

    Thank you.

    Is there a reason that you use VISA events?  It seems that you expect just a character.  Why not to use playback VISA wait for a byte and use the timeout if the byte is not?

Maybe you are looking for