Memory Leak in Mac Pro.  My Mac Pro has 16 GB memory

The memory (as shown in the Activity Monitor) goes from a high of approximately 11 GB free memory to a low of approximately 50 MB.  The leaked memory seems to be going to "Inactive".  When the memory is on the low end, the Mac Pro is very slow, sometimes freezing for several seconds.  Does anyone know what the problem could be?

An update to my original discussion message.  Now the Mac Pro has some extreme lag times when accessing programs, deleting files, copying files, etc.  This occurs even when the free memory as shown in the Activity Monitor is high (over 8 GB).  If anyone has an idea of how to correct this problem, please let me know.

Similar Messages

  • Lightroom 2.3RC and Fast MBP Mac 10.5.6 Still Has BIG Memory Issue

    Lightroom 2.3RC still have a big memory issue on my Macbook Pro (Feb 2008) with 4GB of RAM both in 64bit and 32bit mode. After working on photos in a catalog (using Activity monitor) Lightroom causes my Free Memory to hover around only 10MB or less (causing Lightroom to continually hang or crash) while Inactive RAM sits at 1.5GB! Lightroom should be using this Inactive RAM rather than taking my Free RAM down to nearly nothing and causing freezes or crashes.
    This is not as much of a problem in 2.2 32bit mode, but is a problem on 2.2 64bit mode. However, now with 2.3RC this is a problem on both the 32 and 64bit modes. Please Adobe address this huge huge huge memory problem in Lightroom. Why does Lightroom 2.2 32bit handle memory pretty okay but not Lightroom 2.3RC 32bit mode or 64bit mode? Why did 2.3RC break what for the most part worked in 2.2 32bit mode (even though that wasn't too great either).
    Also I am only running Lightroom (no other programs). I admire the product Adobe, but this problem has persisted far too long and is making Lightroom unusable.

    Hmm. I've been sticking with 2.1 until hearing widespread reports of stability. Every time I checked the forums, I didn't like what I heard about 2.2 so I stayed away. I dropped by to see what the Mac users thought of 2.3. Have you tested on another machine? I assume 2.1 was good for you? Can't wait to see what others are experiencing.

  • IPod touch resets frequently and has low memory, 3rd generation iPod touch resets frequently and has low memory

    Ipod touch resets frequently it refreshes constantly Is that normal? Is this 4th generation really low on memory?

    The Basic Troubleshooting Steps are:
    Restart... Reset... Restore from Backup...  Restore as New...
    Restart / Reset
    http://support.apple.com/kb/ht1430
    Backing up, Updating and Restoring
    http://support.apple.com/kb/HT1414
    If you try all these Steps and you still have issues... Then a Visit to an Apple Store or AASP (Authorized Apple Service Provider) is the Next Step...
    Be sure to make an appointment first...

  • KeyboardFocusManager reason for memory leak?

    Hi all,
    with a memory leak detector we found that our application has massive memory leaks after opening and closing a JDialog and the reason we found was the following:
    The KeyboardFocusManager has a private static HashMap in which the actual focus in each window is stored. This is done by storing key/value-pairs in the HashMap with window as a key and the Component having the focus on this window as the value. Now you can throw the reference to the component away by using e.g. theComponent.setEnabled(false) - the KeyboardFocusManager then stores the pair window/null in the HashMap - but we didn't find any callable method to remove a key/value-pair from the HashMap and so the reference to the JDialog (as the key!!) stays resident and we have the reason for the memory leak. Now I have a few questions to this problem:
    1. Is it right in your opinion, that there is no method to delete the entry from this Hashtable?
    2. If this is the case - we have the opinion that there must be a good time to delete this entry (e.g. when disposing the dialog). Do you see if there is an obvious reason that this opinion is false?
    3. If no do you think this problem can be accepted as a bug by sun
    Thanks in advance and greetings from
    Holger

    I have been seeing similar behavior; I too have not found all the
    leaks. I think I have slowed the allocation by replacing some of my
    'build array' functions with the combination of 'initialize array'
    followed by 'replace array subset'. The drawback to doing it this way
    is that you have a fixed maximum number of elements allocated just once
    rather than allowing an array to grow incrementally. Please let me know
    if you try removing build arrays and if that helps.
    By the way, there is a checkbox under the options menu to deallocate
    memory as soon as possible - if you don't mind that your program runs
    more slowly, this may help to avoid the problem, at least temporarily.
    -vinny
    ciossek wrote:
    > dear all,
    > my labview program needs an increasing amount of memo
    ry when running
    > (at the time about 12k/s) which leads to swapping memory on my hdd.
    > i have found out that calling cluster references like Controls[] or
    > decos[] leads to this kind of memory leak and made a work around for
    > that (simply calling it only once at runtime) but there are more
    > memory leak(s)which i cannot find. The bugs that i have found
    > searching the labview resources does not answer my problem.
    >
    > does anybody already found out more memory leak problems ?
    >
    > thanks

  • Suddenly, I'm getting a huge memory leak

    Since somewhere in Firefox version 36 and continuing to the present (ver 37.0.1), I am getting a major memory leak. I am using Mac OS 10.9.5. And this is what I've done so far: reduced the number of tabs (now at about 4 or 5). Have a minimal amount of plugins and extensions. Maybe 5. I've reset Firefox but the leak still occurs.
    This happens when I leave Firefox open overnight. It's only been happening for about the last month. In the morning I find that all my apps have been paused for lack of memory. Looking at the activity monitor I see that my kernel_task is using 9.5GB of memory (when it should be about 1GB). Quitting Firefox solves the problem. But this has never happened before.
    Also, sometimes Firefox will crash saying the Shockwave plugin quit. I have updated to the latest Flash plugin but it still happens.

    The three Add-ons you mentioned are extensions (Firefox/Tools > Add-ons > Extensions).
    Note that an extension like Firefox bug can cause issues with memory leaks.
    If it works in Safe Mode and in normal mode with all extensions (Firefox/Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.
    Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: Firefox > Quit Firefox; Linux: Firefox/File > Quit)
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    You can try to close the browsing area and only leave the menu bar visible to see if the leak still happens.
    What I meant above was plugins like Flash or Java (Firefox/Tools > Add-ons > Plugins) that might be used on tabs if you keep the browsing area open with some tabs with web pages.
    *https://support.mozilla.org/kb/Troubleshooting+plugins

  • Memory Leak in BlazeDS

    I have used BlazeDS in an  application to push the data in realtime. However, we have been  experiencing a heavy memory leak in the application. The application has  a scheduler that pushes the data every one minute into the default  queue. Without any browsers opened, the appication remain stable. And  closing the browsers also cleans up the FlexClient object and other  associated objects for that browsers. But the leak occurs when we open  and keep browsers for a long period, say 2 to 3 days. The memory usage  of application gradually increases and throws a  "java.lang.OutOfMemoryError: Java heap space" Exception. On analyzing  the HeapDump, I found that there are thousands of AsyncMessage Objects  in the memory, not getting garbage-collected. This the channel definiton  congured in services-config.xml file
            <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
                <properties>
                    <polling-enabled>true</polling-enabled>
                    <polling-interval-seconds>4</polling-interval-seconds>
                    <invalidate-session-on-disconnect>true</invalidate-session-on-disconn ect>
                </properties>
            </channel-definition>
    Does anyone know the cause of this issue and how it can be overcome. Please help.

    We also have the same problem. The JVM goes out of memory every 24 - 50hrs. I have documented a working fix for the problem on the JVM side.
    http://in-finite.me/fixing-blazeds-polling-amf-memory-leak/@

  • Memory Leak in .swf

    Memory Leak issue with CS4
    Using CS4, we have a memory leak and I can not find the
    source of the problem.
    http://tiny.cc/O7D3e here is the
    link to the testing site. If you take a look at your task manager
    you will see it your RAM will continue to increase even after two
    or three cycles. It does not stabilize.
    We are using FlashEff | Flash Effects Component in order to
    generate the smooth transitions. However, I have done some
    debugging and even completely deleted the plug n from the file and
    it still continually leaks memory. Does anyone have any possible
    solutions or causes for this.

    One idea - there is a separate stack of memory in the flash
    player where loaded classes in separate application domains exist,
    and these classes are not being garbage collected....however, there
    is a line in adobe's documentation here:
    http://livedocs.adobe.com/flash/9.0/main/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Liv eDocs_Parts&file=00000327.html
    under "Usage C" :
    quote:
    Having a new application domain also allows you to unload all
    the class definitions for garbage collection, if you can ensure
    that you do not continue to have references to the child SWF.
    Given that, as far as I can see from this code, there is no
    reference to the loaded .swf maintained....it seems to me like the
    loaded data (graphical assets AND classes) should be garbage
    collected - but, while you WILL see a slight drop in memory after
    the removal of the SWF, the overall memory continues to increase
    the more you do it. Could Adobe be mistaken?

  • Memory leaks with Third party classes

    Hello all,
    This is fairly known problem. But I guess, my problem gives a new dimention to the problem.
    I have an application which is developed by me. This application ideally needed to use third party classes ( obviously no source code is supplied ). These third party classes provide extra functionality required.
    The problem is, when I don't use third party classes in my application, every thing is fine. When I include third party classes, I am having memory leaks.
    Then I tried to investigate memory leaks with Optimizeit tool. It is new to me. As of now, I understood, we can identify where the memory leaks are occuring.
    finally the problem is, in order to solve this, I need some patches in the code. But I don't have source code for those classes. How to solve this problem?
    For example,
    I use a third party classes in my code like this,
    ThirdPartyMemoryLeakClass obj = new ThirdPartyMemoryLeakClass();
    This 'obj' is made static, as it takes lot of time to create this object. Obviously this object contains several references to other objects, which I can't control.
    In the process of reusing this object, I am getting memory leaks.
    Any ideas regarding, how one has to deal this type of situations? What are the issues involved with this case? Are there any similar problems, which have been solved? are most welcome.
    many thanks for your time.
    Madhav

    Decompile it using jad. Find leak.Yes, I too got the idea and tried to decompile those classes and recompile. I had some problems while recompiling. Is this is the only way to get rid of this problem?
    I was refering to powersoft.datawindow.DataStore class. Does any body here has worked on these?
    Can you suggest me how to find the memory leak causes? if you were needed to find out memory leak causes, what would be your approach?
    Madhav

  • Memory leak and char[] ?

    Hello all,
    I'm not sure whether this post should be here or in WebLogic section, so correct me if I'm wrong.
    I'm working on JDeveloper 11.1.1.3 while deployments are made on standalone WebLogic 10.3.3. This thing occurred in previous versions also.
    With every deployment WebLogic increases it's used memory until the famous PermGen space error, which is after about 5-6 deployments.
    I'm doing my best to understand how to use memleak detection tools. I've switched JDev and WL from Sun jdk which was used before to JRockit, same thing happens. Both JDev's memory profiler and JRockit mission control show something that I really do not understand. char[] uses around 30% of heap space and keeps growing with deployments, next is String with 8%. I never use char in app.
    Am I looking at the wrong thing? Is it normal for char[] to increase on WebLogic on deployments? Does anyone know how to check other things and what to check? Someone on other forums mentioned it would be useful to check if ApplicationContext keeps initializing over again on deployments. Does anyone know how to check this?
    One more thing, I have successfully deployed app on Tomcat, and Tomcat said there is a memory leak in app, but could not tell anything specific.
    I'm kinda lost in this :(

    It is normal for the PermGen space of the Sun's JVM to get filled after several re-deployments. PermGen stands for "permanent generational". This space is used by classes that is unlikely to need to be garbage-collected, so they are placed in this memory space that is never garbage-collected (for example, the Class instances). When you redeploy an application, a new class loader instance is used and it instantiates new Class instances that fill up the PermGen space. But why this happens on JRockit either, I could not explain.
    We have experienced memory leaks related to classes and components that use native memory. For example, we have had significant memory leak when using Oracle's JDBC OCI driver. We were not able to solve this problem, so we switched to JDBC Thin driver (which is very performant and stable today comparing to some years ago). If you are using Oracle JRockit, you can monitor the overall memory usage by the following JRockit command executed at OS command line:
    jrcmd <jrockit_pid> print_memusage>where <jrockit_pid> should be replaced by the JVM process ID.
    If you suspect existence of native memory leaks, then have a look at the article Thanks for the memory for explanations about how Java uses native memory.
    Dimitar

  • Memory leak on SunOne Web Server 6.1 on application reload

    Hi!
    I am pretty sure that i have found a memory management problem in
    SunOne Web Server 6.1 .
    It started with an OutOfMemory error we got under heavy load . After
    some profiling with Jprofiler i didn't find any memory leaks in the
    application.Even under heavy load (generated by myself) i can't find
    anything ,more, i can't reproduce the error! The memory usage is
    about 20Mb and does not go up .
    However it is pretty simple to see the following behavior:
    [1] Restart the server (to have a clear picture) and wait a little for
    memory usage to stabilize.
    [2] In the application dir. touch .reload or one of the classes:
    The memory usage goes up by another 50Mb (huge amount of mem. taking
    into account the fact that it used only 20Mb under any load befor).
    Do this another time and another 20Mb gone etc..
    The JProfiler marks the memory used by classes . And it can be
    clearly seen the GC can't release most of it.
    I AM sure this is not the application that takes all the memory.
    Another hint : after making the server to reload application i can see
    that the number of threads ON EVERY RELOAD is going up by ~10-20
    threads .The # of threads goes lower over time but not the mem usage.
    My system:
    Sparc Solaris 9 ,Java 1.4.2_04-b05, Sun ONE Web Server 6.1SP5
    Evgeny

    my guess is that - because of '.reload' , web container tries to
    recompile all the classes that you use within your web application and
    hence the memory growth is spiking up.What do you mean by "tries to recompile"?The classes in
    Web-inf are already compiled! And i have only ~5 jsp's .
    (the most part of the applic. is a complicated business logic)
    If you are talking about reloading them ,yes,that's the purpose of .reload,
    isn't it? :).But it seems that container uses the memory for it's own
    classes: the usage of memory for my classes don't really grow
    that much (if at all) after reload (according to profiler)
    Also the real problem is that the memory usage grows to much for
    too long (neither seen it going down) and thus ends with OutOfMemory.
    if you are seeing the memory growth to be flat in stress environment,
    then I am not sure that why do you think that there is a memory leak ?There is no memory leak in stress environment.
    There is memory leak while reloading the application.
    It is a memory hog for sure (~20-30Mb for every reload).
    Memory leak?It seems that way because i can't see memory usage go
    down and after a lot of reloads OutOfMemory is thrown.
    also, what is jvm heap that you use ? did you try jvm tune options like -
    XX:+AggressiveHeap ?256Mb.I can set it bigger ,but how do i know that it will not just delay
    the problem ?
    Thanks for response.
    Evgeny

  • Dbx SEGV signal encountered while memory leak checking

    Good morning,
    Last week, I have encountered the following problem while debugging a UNIX Solaris on a SUN server:
    Running the program without memory leak checking goes fine.
    Running the program while memory leak checking gives following error message:
    RTC: Enabling Error Checking...
    t@1 (l@1) signal SEGV (no mapping at the fault address) in __rtc_memcpy at 0xffffffff7312dc98
    I have already mentioned the problem on the SUN forum (as it is dbx related), but as the problem is not solved by installing patches, using more recent dbx versions and, most important, as a "where -l" dbx command reveals that the problem is located within an Oracle file, I start to believe that the problem is not caused by dbx, but by Oracle.
    The SUN forum post can be found back using following URL:http://forum.java.sun.com/thread.jspa?messageID=9575156
    The result of the "where -l" command is the following:
    (dbx) where -l
    current thread: t@1
    [1] libwtc8.so:_init(0x0, 0xffdfffff, 0xffffffff7f72a3f8, 0xffffffff7f72a9e8, 0x200000, 0x400000), at 0xfffffffd22501180
    [2] ld.so.1[L]:setup(0xffffffff7f72a9e8, 0xffffffff7f72a158, 0xffffffff7f72d838, 0xffffffff7f72a140, 0x3, 0x1001403c8), at 0xffffffff7f60f8fc
    [3] ld.so.1[L]:_setup(0x2710, 0x2710, 0xb00, 0xffffffffffffffff, 0x0, 0xffffffffffffffff), at 0xffffffff7f61d8c0
    [4] ld.so.1[L]:_rt_boot(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xffffffff7f604ce0
    <UNIX prompt>find / -name libwtc8.so 2>/dev/null
    <internal directory>/oracle/lib/libwtc8.so
    <internal directory>/oracle/lib64/libwtc8.so
    As the "nm" command only reveals a "_init" function for the latter libwtc8.so file, I believe strongly that this is the one referred by by dbx.
    In case you need more information (e.g. as far as Oracle versions are concerned), could you also include the UNIX commands, needed for retrieving this information?
    Kind regards
    Dominique

    The statement 'while memory leak checking' is not clear. Are u compiling with -g flag or profile flags ? OR using the 'collect' of SUN STUDIO ??
    Can u place the complete trace of CORE using the command 'dbx - core' for further analysis.
    Are U using any STL 3rd party libraries for Linking ?? .
    Place the sample code if possible.
    After going through SUN forum , I realize that there can be an imcompatibility with SOLARIS LIBS and Oracle of 64Bit layer. Are compiling in 64bit or 32 bit ?
    Try 64Bit compilation.

  • Oracle JDBC Thin Driver Memory leak in scrollable result set

    Hi,
    I am using oracle 8.1.7 with oracle thin jdbc driver (classes12.zip) with jre 1.2.2. When I try to use the scrollable resultset and fetch records with the default fetch size, I run into memory leaks. When the records fetched are large(10000 records) over a period of access I get "outofmemory" error because of the leak. There is no use increasing the heap size as the leak is anyhow there.
    I tried using optimizeit and found there is a huge amout of memory leak for each execution of scrollable resultsets and this memory leak is propotional to the no of records fetched. This memory leak is not released even when i set the resultset,statement objects to null. Also when i use methods like scrollabelresultset.last() this memory leak increases.
    So is this a problem with the driver or i am doing some wrong.
    If some of you can help me with a solution to solve this it would be of help. If needed i can provide some statistics of these memory leaks using optimize it and share the code.
    Thanks
    Rajesh

    This thread is ancient and the original was about the 8.1.7 drivers. Please start a new thread. Be sure to include driver and database versions, stack traces, sample code and why you think there is a memory leak.
    Douglas

  • How to define the memory leak in stability test

    Hi
    Usually, we run our system with 70% CPU load for 72 hours for stability test (on solaris 10), because some plugin of our system is using mtmalloc, and we use prstat to monitor the memory of each plugin. But because of the complex memory usage of our application, we don't know when the application will use the Max memory, and because of the "mtmalloc", the memory showed by "prstat" will not released but continually increased.
    So fro the test point of view, there is the risk of memory leak, but actually, there may be no memory leak, so my question is how to define the memory leak in such condition.

    kevin wrote:
    Thank you for the input and all the info.
    isn't java heap the same as memory allocated to the java process in my weblogic
    starup script ?The heap is sized by the -Xmx and -Xms parameters you pass on the java
    command-line. The permanent generation is separate.
    >
    let me also download jprobe and try to run it and see what it gives me.
    I'd start by running with -verbose:gc. I'd want to know whether you're
    running out of heap or permgen space.
    -- Rob
    kevin
    Rob Woollen <[email protected]> wrote:
    Unfortunately memory leaks are not fun to track down even with tools.
    I'd first suggest determining whether you're running out of space in
    the
    permanent area (where classes are loaded), or you've exhausted the java
    help space.
    I'd start by adding -verbose:gc. Look at the gc messages right before
    you hit the OutOfMemoryError. If there's plenty of space left, I'd
    suspect you're running out of perm space. Search these newsgroups and
    the web for MaxPermSize, and you should see plenty of info.
    If you're running out of java heap, tools like jprobe and OptimizeIt
    are
    helpful. If you can tell me a little more about your application and
    how you're testing it, I can offer some more tips.
    -- Rob
    kevin wrote:
    Iam new to JAVA and weblogic. I have an application that runs out ofmemory time
    and again.
    please let me know how to pin point this problem and moreover, howto interpret
    or understand that there is a problem. I have downloaded JPROFILE tool,but it
    is very confusing to understand what is goin on in this tool.
    If somebody can let me know how to interpret and understand the memoryleak, that
    will be great !!!
    thank you.

  • Memory leak in NSUserDefaults

    Hi, I have a iphone photography App. In my app, user may open many images. Each time user opens a new image, I will save the image to NSUserDefault so that next time user starts my app, the last image will be loaded.
    Here is my code, (I call this method everytime user opens a new image)
    -(void) saveDefaults:(
    NSUserDefaults *standardUserDefaults = [NSUserDefaults standardUserDefaults];
    if (standardUserDefaults){
    NSData* imageData = [NSData dataWithBytes:(void*)someMemoryBuffer length:lengthOffBuffer];
    [standardUserDefaults setObject:imageData forKey:@"MyImage"];
    I do not call [standardUserDefaults synchronize] each time I put a new image in NSUserDefaults. I call it to commit saving image to NSUserDefault only when my program ends.
    It seems that there is a memory leak. I used PerfermanceTool, it does report any memory leak, but I can see that the memory token by my App increases everytime I call "saveDefaults" and perfermanceTool points the increase of memory to the "saveDefauts" function. Is there any memory problem in my code.
    Thank you very much.
    ff

    As I have neither an iPhone Developer account nor an iPhone, I can't help very much. Try this link. I don't know if it will help because I can't sign in. You could save your data in SQLite.
    You could follow these instructions. Try looking at the official Apple documentation instead.

  • Memory Leak in Publish-Subscribe Notification

    I am using publish-subscribe notification for async-notification on LINUX( ORACLE 8.1.7). Before doing it, I read a document(OCI Programmer!/s Guide) about publish-subscribe notification(chap.9).
    I created Queue(AQ) in database and registered callback function using 'OCISubscriptionRegister()'.
    All operations are done succesfully , but when OCISubscriptionRegister() is called, memory leak seems to occur. I check up the memory leak using LINUX system call( 'top' and 'vmstat' ).
    Does anyone have any idea or experience of this problem?

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Lee Sung-won ([email protected]):
    Thanks for your reply..
    I have something to ask you. where can I get a document listing the bug?<HR></BLOCKQUOTE>
    null

  • Memory Leak in Applet

    Hello Good people,
    I am facing a troubling memory problem in my applet.
    Apparently, it suffers from some major memory leaks and every time I reload my applet the memory is consumed with additional 5Mb. I am looking for ways to work around this (or better yet to completely solve it) - I've noticed that the JVM is still alive when the applet is disposed and destroyed, it is not being killed until I close the parent IE windows. Because of this, the heap of the JVM is never totally cleaned and after several applet invocations I get to the heap's limit and everything is stuck.
    I am looking for ways to control the JVM - is there a way to manually reset its memory or even kill it through javascript after the applet is disposed?
    Thanks a lot!
    Tal

    Hi Andrew,
    I appreciate your help but I remember that in the research I did when I just started the project I have found that the web start technology is not suitable to me because it always open a new window and I need my applet to be embeded in an exisitng window.
    Do you know differently?
    Thanks,
    Tal

Maybe you are looking for