Flex 4.5 - s:Window - s:DataGrid - Memory Leak?

Hi All,
We're trying to clean up Air windows and noticing some odd behaviour.
Here is the case:
We have a spark window that contains a spark datagrid, this datagrid is bound to a dataprovider which is a model in the main application.
When we close the window, there is ALWAYS one instance of MyWindow that remains in memory.
And looking at the trace of the window does not give much information...
Has anyone seen this before? Alex, you've helped us a lot before with memory issues, can you shed some light please?
Thank-you!
We have a simple test case: ( Didn't wire the close handler, so make sure to use the close button.)
Main.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication
          xmlns:mx="library://ns.adobe.com/flex/mx"
          xmlns:fx="http://ns.adobe.com/mxml/2009"
          xmlns:s="library://ns.adobe.com/flex/spark"
          xmlns:domain="domain.*"
          >
            <fx:Script>
                    <![CDATA[
                              import mx.core.Window;
                              public var window:MyWindow;
                              protected function openWindow(event:MouseEvent):void {
                                        window = new MyWindow();
                                        window.model = this.model;
                                        window.open();
                              protected function closeWindow(event:MouseEvent):void {
                                        window.close();
                                        window = null;
                    ]]>
          </fx:Script>
          <fx:Declarations>
                     <domain:Model
                              id="model"
                              />
          </fx:Declarations>
          <s:HGroup>
                    <s:Button
                              label="Open"
                              click="openWindow(event)"
                              />
                    <s:Button
                              label="Close"
                              click="closeWindow(event)"
                              />
          </s:HGroup>
</s:WindowedApplication>
Model.as
package domain {
           import mx.collections.ArrayCollection;
          [Bindable]
          public class Model {
                      public var collection:ArrayCollection = new ArrayCollection([ { name:'Adobe' }, { name:'Apple' } ]);
MyWindow.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:Window
          xmlns:mx="library://ns.adobe.com/flex/mx"
          xmlns:fx="http://ns.adobe.com/mxml/2009"
          xmlns:s="library://ns.adobe.com/flex/spark"
          width="400"
          height="300"
          >
          <fx:Script>
                    <![CDATA[
                              import domain.Model;
                              [Bindable]
                              public var model:Model;
                    ]]>
          </fx:Script>
          <s:DataGrid
                    dataProvider="{ model.collection }"
                    />
</s:Window>

Hi Alex,
We've tested with this and discovered that any datagrid in a spark window assigned a dataprovider results in always one instance of the window staying in memory.
Here is what we tested:
Window with nothing in it = gets collected.
Window with datagrid and no dataprovider = gets collected.
Window with datagrid and no dataprovider but "model" is passed from main = gets collected.
window with datagrid and local dataprovider (inline) = get pinned.
window with datagrid and passed "model" as dataprovider = get pinned.
Tested this on two computers with FB 4.5.1
Thanks again!
I cannot see where I can post fxp sorry. So I am posting code adjustments here showing the window with just inline dp.
Modified MyWindow.mxml:
<?xml version="1.0" encoding="utf-8"?>
<s:Window
          xmlns:mx="library://ns.adobe.com/flex/mx"
          xmlns:fx="http://ns.adobe.com/mxml/2009"
          xmlns:s="library://ns.adobe.com/flex/spark"
          width="400"
          height="300"
          >
            <s:DataGrid id="dataGrid">
                    <s:ArrayCollection>
                              <s:DataItem key="1000" name="Abrasive" price="100.11" call="false"/>
                              <s:DataItem key="1001" name="Brush" price="110.01" call="true"/>
                              <s:DataItem key="1002" name="Clamp" price="120.02" call="false"/>
                              <s:DataItem key="1003" name="Drill" price="130.03" call="true"/>
                              <s:DataItem key="1004" name="Epoxy" price="140.04" call="false"/>
                              <s:DataItem key="1005" name="File" price="150.05" call="true"/>
                              <s:DataItem key="1006" name="Gouge" price="160.06" call="false"/>
                              <s:DataItem key="1007" name="Hook" price="170.07" call="true"/>
                              <s:DataItem key="1008" name="Ink" price="180.08" call="false"/>
                              <s:DataItem key="1009" name="Jack" price="190.09" call="true"/>            
                    </s:ArrayCollection>
          </s:DataGrid>
  </s:Window>
Modified main.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication
          xmlns:mx="library://ns.adobe.com/flex/mx"
          xmlns:fx="http://ns.adobe.com/mxml/2009"
          xmlns:s="library://ns.adobe.com/flex/spark"
          xmlns:domain="domain.*"
          >
            <fx:Script>
                    <![CDATA[
                              import mx.core.Window;
                              public var window:MyWindow;
                              protected function openWindow(event:MouseEvent):void {
                                        window = new MyWindow();
                                        window.open();
                              protected function closeWindow(event:MouseEvent):void {
                                        window.close();
                                        window = null;
                    ]]>
          </fx:Script>
            <fx:Declarations>
                      <domain:Model
                              id="model"
                              />
            </fx:Declarations>
            <s:HGroup>
                    <s:Button
                              label="Open"
                              click="openWindow(event)"
                              />
                    <s:Button
                              label="Close"
                              click="closeWindow(event)"
                              />
          </s:HGroup>
  </s:WindowedApplication>

Similar Messages

  • Adobe Reader X and Windows 7 Enterprise Memory Leak

    Hi I am using Adobe Reader X with Windows 7 enterprise when reading a 8000 page document when I do a search I notice that the memory on my machine starts to creep up typically 1Mb per search this will continue to rise to over 300Mb as the document is used until it reaches a point that it freezes the machine, The only way to recover is Ctrl-Alt-Delete and cancel the task. Has this been observed by other users?

    Good day,
    Could you provide some additional details about both the file and your system's configuration?
    What version of Adobe Reader X do you have installed? (Help > About Adobe Reader)
    If you haven't updated to 10.0.3, please do so and see if the issue persists.
    How was the PDF file you're searching created?  (File > Document Properties > What does the PDF Producer line say?)
    Are you experiencing this with multiple files?
    Have you installed SP1 for Windows 7?
    Regards,
    David
    Acrobat Community Manager
    Adobe Systems

  • Windows 7 chkdsk memory leak?

    I was wondering if anyone else has noticed extremely high RAM usage when using windows 7's chkdsk.  I've used chkdsk on the same USB flash drive on my XP, vista, and 7 machines, and the memory usage is as follows:
    xp : 20 - 30 MB (Depending on stage)
    vista : 2.5MB
    7 : about 25MB per second running (e.g. after chkdsk has been running for 10 seconds it will be using 250MB, after 2 minutes it will be using 3.0GB)
    I am monitoring memory usage using task manager.  I actually have two machines running windows 7 7100 release candidate (x64) and the I noticed the problem on both.
    The problem is easiest to duplicate if you run chkdsk on a drive other than your OS drive (so you can actually have task manager open while it runs as opposed to running after a reboot), and if you run a check that will take a long time.  chkdsk /f on a large hard drive works fine, or chkdsk /r on a smaller hard drive will work as well.  It doesn't seem to depend on which stage it is in - the memory usage balloons during stage 2 of a chkdsk /f on a (full) 1TB hard drive I have, and it happens during stage 4 of chkdsk /r on a half-full 32GB USB flash drive as well.
    I would be interested to see if anyone else can duplicate this.

    Noel, Concerning your statement:
    If you are having to run CHKDSK regularly, something's wrong with your system, or with the way you do computing.
    The file system does not and
    should not normally become corrupted!
    In my case, I run chkdsk/r quite frequently because I am an IT consultant (since 1985).  I regularly take out hard drives from client systems, and attach it to an external USB or eSata box, and attach it to a known working system. Then I can run
    "out of band" antivirus and chkdsk types of analysis and repair. Recently, on a 3TB drive (that ultimatly chkdsked perfectly clean), it took about 9 hours to complete the chkdsk/r. Frankly, I wouldn't have minded if the check took 24 hours, but I
    (and my client) DID mind that the otherwise useful quad-core 10GB workstation, was incapacitated beyond usefulness during this period.
    This 3TB disk only had about 300 data files on it, and was less than 10% full. checking at a rate of about 20k clusters/sec over esata.
    If it is grabbing this memory for the allocation tables, it should release it BEFORE stage 5 (free space scanning).
    It may be design... but it looks, acts, feels, tastes, smells, like an arrogant designer flaw. And it's obvious many of us have stepped in this poop.
    However, i'm willing to negotiate. Make it default, but give me a flag to specify maximum memory allocation. Thank you for your consideration. rich
    This thread really saddened me. It is filled with with so many opinionated people, which on any other forum would be classified as trolls and given suspensions or banned. People like Noel and Igor have only aggravated others that are suffering from this
    bug.
    Yes, I say bug - allow me to provide my reasoning.
    1) Windows is all about multitasking. This memory consuming design goes directly against everything Microsoft has aimed to achieve over the last few decades.
    That's really the only important point. Only the bootable form of the tool should consume all memory. System drives should be forced to run the bootable form, but external/USB/eSATA drives should be properly detected and be checked without causing all these
    problems reported in this thread.
    To expand upon that point...
    2) Tools like SATA docks are extremely common now. As an IT tech I probably scan at least a half dozen drives per week. There's hundreds of thousands of other people doing the same thing... maybe millions. This is not a fringe usage scenario.
    3) It's not uncommon to see one machine scanning 30 or 40 drives (rackmount, etc.) after an unexpected power failure at big companies/datacenters. Those drives run linux filesystems. Incapacitating one computer to check one drive at a time is extremely silly.
    Even if it makes it twice as fast, you lose out on having zero parallelization.
    Those are really the main reasons. Now, let me tell you an interesting story from yesterday.
    Normally chkdsk has worked fine for me, but yesterday I encountered this bug - I received a drive that could not be cloned with Windows tools, and could not successfully be chkdsk'd (unless I fire up a Vista/XP DVD) - both chkdsk /f and chkdsk /r fail under
    Win7, by consuming 99% of memory and causing everything to crash. (Backup software, background programs, then chkdsk itself locks up and stops doing anything.)
    This is a fringe case for sure, but it's caused by a bug - a design defect - something that would cause me to fire a coder if they made such a silly backwards assumption.
    Now for the details - *drumroll* - the drive that I'm checking is approximately 60GB large (80GB PATA drive with one main partition and one small recovery partition), and appears to have 18.2 million file records. (YEAH - fringe case) It completely incapacitates
    the Win7 chkdsk, but not the Vista or WinXP chkdsk. (Which, btw, check it over far faster. I suspect the simpler less memory hungry algorithm is faster than cannibalizing as much pagefile as it can get...) chkdsk /f takes many hours to run, and chkdsk /r did
    not complete overnight, but was finished by the end of today. I first got the idea to check over this drive when I heard it clacking away constantly for seconds for every single task. (Clicking a shortcut, clicking the start menu, etc.) I fired up Defraggler
    and noted 100% of the squares in the graphic were yellow. Despite that 70% of the drive is empty. Something has seriously gone wrong with NTFS on the main partition.
    Anyway, like I said, I'd fire the coder that made such an assumption if he refused to learn and correct it. Logic holes like this are exactly the kind of thing that create holes/exploits for viruses - although in this case it's a performance bug rather than
    security bug. Regardless, it's sloppy coding that didn't plan for fringe use cases (< 1%), and thus fails completely when encountering them. Proper behaviour (IMO) would be to heavily encourage rebooting to check a drive in the GUI CheckDisk, but allowing
    the cmdline chkdsk to run properly in Windows for non-system drives without devouring all available memory.

  • Ideapad Flex 14 issue with Windows 10

    I had this with Windows 8.1 for almost 2 years.  It works fine.  Now i upgraded it to windows 10 and everything went ok but both Wired internet connection LAN and Wireless internet connection was not working.  I have downloaded the drivers by myself and also what Lenovo support suggested but it is not working.    Has anyone with Lenovo Flex 14 upgraded to Windows 10 successfully. In some ways Lenovo was advocating to update to windows 10 but they don't want to help me but send me to premium support where i have to pay :-( Thanks in advance for any help.  

    This really is a driver issue with Nvidia SLI or not, but it has to do with this monitor and possibly it's 75Hz refresh rate.  I thought I'd share and hopefully Acer can work with Nvidia to make their new monitors compatible with Win10.  I know we are using bleeding edge tech here, I don't mind doing the troubleshooting as long as someone acknowledges the issue and will fix it. Serious memory leak with 355.60 as soon as the monitor goes to sleep. I've done extensive testing with poolmon, xperf, etc to see if any other drivers cause this, but nothing, this is a brand new win10 fresh install. Easiest way I can show this is via MSI afterburner. Monitor is set to sleep after 1 minute so I can do this quick test.    You can see less than 2 minutes in, pagefile usage already jumped up 4gb.Unless I wake the monitor, this will eventually eat up all virtual memory resulting in:  

  • LV memory leak - How to use windows API SetProcessWorkingSetSize (from Kernel32.dll)

    Hi fellow LV'ers
    Okay - this is a bit tricky, but i'll try and explain the problem, then ask for the solution, because it may be that someone knows a better way to deal with this.. might get a bit long, sorry - if a solution comes up this will enable all of us to make more memory efficient LV code so please read on..
    Here is the deal:
    When building even a very simple LV executable, looking at the windows task manager will yield a rather large amount of memory allocated for such a small program - and the only way to free this up is by physically clicking the windows minimize button, then suddenly the amount drops to only a few MB and upon maximizing the window again the memory consumption will increase somewhat again, but for a simple VI build to an exe this move may change the consumption from +70MB to less than 15 MB.. This is irregardless of the code you put in the VI, so no coding example in this post as it is how LV works - you can even test it with the development environment - look at the task mgr and check LabVIEW's memory consumption, minimze ALL open NI windows incl project explorer etc, and you will see a significant decrease in memory usage even after maximizing again.. This has annoyed me since day one, but since RAM is a near zero cost these days it is not something I stay awake at night to think about.. However - I have moved into the "publish to web" tools now, wanting to do a remote monitoring part for my application for my customers to experience increased usability from the software i sell them..
    All is well, publishing is really easy (i use the monitor function, NOT the embeded, as customers need not have Labview RunTimeEngine installed, because they might look at it from a non RTE supported platform such as a mobilephone web browser)
    Everything is working fine also for the build application. However - I have noticed that once users start to remote monitor the running application - memory consumption of the running LV application starts to increase - and it keeps doing so - to such an extend that you can drain the computer complete and run off the cliff with a windows error... This is off course not very productive for me, being specialized in measurement applications that usually runs for a long period of time - I initially thought that I had done some poor programming in the VI used to display on the webpage - but it turns out that I can reproduce this behaviour with a simple boolean on an empty front panel..
    NI support has been informed, and they admit there is a problem, but so far solutions from them has been a bit too exotic for my taste, and thus I'm seeking the help of fellow LV programmers...
    You see - The method to solve the increasing memory consumption, is the exact same as mentioned above..minimize the application running with the "minimize" button and all memory will be freed, as soon as you maximize the application and users are viewing it remotely, the memory usage raises again, and history repeats... As previously mentioned, minimizing the window via normal LV calls to property nodes does not yield the same result, nor does a request deallocation of a VI(When you profile a project, there are no VI's increasing in memory, it is the LV process it self doing it) 
    After many many hours googling I stumbled upon this:
    http://support.microsoft.com/?kbid=293215
    I believe trimming the process with SetProcessWorkingSetSize would solve this problem, and now I would really like to be able to do this in my program, so that users are not forced to minimize the program every X hour depending on their system size...
    However - I have absolutely NO experience in calling windows API from LV, i need someone with that knowledge to provide an example of how to call this.. I've looked at examples on how to do calls to windows API - there is an example in this forum with some llb's in it, and I have gained a fair understanding of how parameters are passed between the calls, but none of those include the "hProcess" handle that is apparently needed for this specific winAPI call to work - Anyone in this forum with the knowledge on how to obtain this handle from a VI, if at all possible, and could provide an example VI for me to use - or even better , someone with the knowledge of how to do this within LV it self??
    Your help is much appreciated
    Best Regards
    Jacob
    LV8.6.1 patch something
    Win XP 
    Solved!
    Go to Solution.

    Hi Enrico
    Finally I can give something to the community that has given me so much  :-)
    The "official" statement is that "yes we know it is a problem".. Not sure what that will do to the future.. 
    I have the problem on 8.6.1 as well  - and in fact it is a general LV problem, that I first time reported to NI with LV8.2 as I was pissed by the fact that even the smallest exe file would consume + 50MB of memory until you manually minimized the window. Well - thanks to the feedback from Cosmin I seem to have solved the problem.
    I most warn that having started to "empty process" once in a while has led to occasional program crashes in the lethal "app.exe performed an illegal action and is closed" windows dialog - however what I did was to move the webserver to a seperate exe file and then communicate the data that I want to use via datasocket in a cluster.. It works like a charm and I simply stall the single thread that the webserver is running when ever the empty process is called and I have not seen a crash since then.. (the initial implementation was done in the main app with 4 parallel loops running, and I guess that was a disaster waiting to happen)
    Either way - what I have done is made a VI that at a user defined interval calls the empty process, simply by getting the .exe name from the task manager of the calling program - it is simple and very effective. I call it every 5 minutes - needless to say that flushing too often will most likely kill performance of the system. I have not noticed problems with VM - are you sure you are not storing large arrays or moving around copies of data not used frequently?
    For future reference to this forum, it is attached here including the .dll required to call - it is a LV8.6.1 file as I have not had the time to yet again test every single function of my program for new problems that could occur with upgrading to LV2009 
    I hope this solves your problem..
    best regards
    Jacob
    www.10EaZy.com 
    Attachments:
    EmptyProcess.zip ‏32 KB

  • 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 using CertOpenStore on Windows 2008 R2

    I have a program (runs both 32 and 64 bit ) that when using CertOpenStore results in a memory leak on Windows 2008 R2 only (I haven't tried 2012, but this code has run for years on 2000, 2003, 2008 without issues)
    Sample code to reproduce the issue:
    int main( int argc, char** argv )
    HCERTSTORE store;
    int go = 1;
    while( go ){
    store = CertOpenStore(
    CERT_STORE_PROV_SYSTEM_A,
    0,
    0,
    CERT_SYSTEM_STORE_LOCAL_MACHINE | CERT_STORE_OPEN_EXISTING_FLAG,
    "MY" );
    if( store ){
    //if( !CertCloseStore( store , CERT_CLOSE_STORE_CHECK_FLAG ) ){
    if( !CertCloseStore( store , CERT_CLOSE_STORE_FORCE_FLAG ) ){
    if( GetLastError() == CRYPT_E_PENDING_CLOSE ){
    printf( "!" );
    else{
    go = 0;
    else{
    go = 0;
    Sleep( 10 );
    return 0;
    The callstack for allocations pretty much are all like this  (this is from a 32 bit process on a 2008R2 box)
          HEAP_ENTRY Size Prev Flags    UserPtr UserSize - state
            02e75af0 000f 0000  [00]   02e75b08    0005e - (busy)
            7724dff2 ntdll!RtlAllocateHeap+0x00000274
            745f6017 AcLayers!malloc+0x00000079
            7460dc96 AcLayers!NS_VirtualRegistry::MakePath+0x00000056
            7460e817 AcLayers!NS_VirtualRegistry::CVirtualRegistry::OpenKeyW+0x000000a9
            7460f21a AcLayers!NS_VirtualRegistry::APIHook_RegOpenKeyExW+0x00000036
            743d2641 AcGenral!NS_WRPMitigation::APIHook_RegOpenKeyExW+0x00000024
            7527a246 crypt32!RegOpenHKCUKeyExU+0x00000055
            7527de26 crypt32!OpenSubKeyEx+0x00000108
            7527e4d8 crypt32!OpenSubKey+0x00000015
            7527ed88 crypt32!OpenSystemRegPathKey+0x00000033
            75281a2f crypt32!EnumPhysicalStore+0x00000162
            75281d0e crypt32!I_CertDllOpenSystemStoreProvW+0x0000015c
            752c9fce crypt32!I_CertDllOpenSystemStoreProvA+0x0000006c
            7527e49a crypt32!CertOpenStore+0x0000010e
    Anyone have any ideas of a hotfix available for this?
    thanks

    Might ask them here about this.
    Windows Desktop Dev forums on MSDN
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Memory Leak in Adobe Premiere CC on Windows

    I installed Premiere CC on Windows 7 ( Intel Core i7-3770K [email protected] GHz, 16GB RAM). Software has a serious memory leak. After less than hour working on a very simple project (no rendering, no effects) memory usage  reached 15 GB, at which point Premiere stopped responding. After closing and reopening software memory usage again started to increase. I was testing it by just scrubbing over timeline, no editing, memory usage still slowly crept-up. I called Adobe technical support, they tried to tell me, that this is normal. Right! It is normal to be forced to close and reopen application every hour? I do not think so. I have Premiere CC also installed on my MAC Book Pro, checked memory usage on much bigger project, it was steady, not creeping up, using beween 1 and 2 GB.  I checked forums for this problem, there are several posts, but have not found any response from Adobe regarding this.
    Update:
    Tonight I continued working on same small project, within 2 hours I had to shut down Premiere 3 times. I also limited in setting memory Premier can use, that did not make any difference, usage by Premiere went to maximum - total 16 GB with about 2 GB taken by system and other stuff running. I am monitoring memory usage on resource monitor. Used Physical memory went 100 %, Commit Charge about 60%. This so far happened three times  in a row.
    Adobe, can you hear me?
    Milan
    Message was edited by: milan-to
    Message was edited by: milan-to

    Adobe, can you hear me?
    Not guaranteed when posting here.  Try below instead.
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Having said that, this is not a problem I see on any of the four Windows machines I work on.  And it's not a problem commonly reported here.  So my inclination is to suggest that something may be funky with your install.

  • Memory Leak Lenovo X201 and Windows 8

    Hi,
    I'm having a memory leak issue with my X201 and Windows 8. My system starts almost without memory, taking 6.7 of 7.8 GB RAM.
    More people seem to have the same problem:
    http://answers.microsoft.com/en-us/windows/forum/windows_cp-windows_programs/windows-8-rtm-memory-le...
    I have installed the available beta drivers  but they don't help. Any advice?
    Spec:
    - Windows 8 Enterprise
     - Intel Core i7-620M Processor (2.66GHz, 4MB L3, 1066MHz FSB)
     - Genuine Windows 7 Professional 64
     - Genuine Windows 7 Professional 64 US English
     - 12.1" WXGA LED Panel, 2x2 UltraConnect II antenna; with Camera and Wireless Broadband Upgradeable
     - 8 GB PC3-8500 DDR3 SDRAM 1067MHz SODIMM Memory (2 DIMM)
     - Keyboard UK English
     - TrackPoint with Fingerprint Reader
     - 128 GB Solid State Drive, Serial ATA
     - 5-1 Media Card Reader and Modem
     - ThinkPad X200 Series 9 cell Li-Ion Battery (up to 5 hours life)
      - Country Pack United Kingdom with Line cord & 65W AC adapter
     - Bluetooth w/ antenna
     - Intel Centrino Advanced-N 6200 (2x2 AGN)
     - Integrated Wireless Wide Area Network upgradable

    Does Windows 8 manage memory differently?

  • There appears to be a MAJOR issue (hang/memory leak) in "about:home", also known as the Firefox Start Page, in Firefox 26.0 on Windows!

    There appears to be a MAJOR issue (hang/memory leak) in "about:home", also known as the Firefox Start Page, in Firefox 26.0, on Windows!
    observed on:
    - Windows 7 x64 machine with 12GB RAM and high-performance CPU (core i7-920)
    - Virtual Machine guest running WinXP SP3 (in Oracle VirtualBox) on the same machine
    - Intel Atom D525 netbook with 4GB RAM, running Win7 x64
    Neither of these machines are connected via Sync or anything like that. The Firefox instance on the VM is a fresh/clean install.
    The problem:
    - 100% cpu usage for 10 seconds, memory usage (PF usage in XP) goes up to 1.7GB
    - if "about:home" is the Firefox Start Page, effectively it hangs the computer at Firefox startup for 10 seconds
    - if "about:home" is NOT the Firefox Start Page, startup is fine - BUT if I press the "home" button on the toolbar it loads "about:home" which causes the same issue again

    Thank you cor-el! Your suggestion has solved the problem on my WinXP VM which I was using to test, and I will soon confirm that it has also solved the problem on my primary Win7 desktop.
    To recap:
    - I set "browser.aboutHomeSnippets.updateUrl" to an empty string
    OLD VALUE: https://snippets.mozilla.com/%STARTPAGE_VERSION%/%NAME%/%VERSION%/%APPBUILDID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/
    NEW VALUE: (blank)
    - I deleted the folder \storage\persistent\moz-safe-about+home under the Profile directory
    Actual folder name on WINDOWS XP:
    C:\Documents and Settings\<USERNAME>\Application Data\Mozilla\Firefox\Profiles\<PROFILENAME>\storage\persistent\moz-safe-about+home
    However I have a concern that the '''OLD VALUE''' of "browser.aboutHomeSnippets.updateUrl" will creep back in, in a future update! Can you communicate this issue to someone on the development team?

  • Tuxedo Memory Leak Issue (Tuxedo 8.1 - Windows Server 2003)

    Hi
    We are running tuxedo 8.1, 32 bit with patch level 258 in our windows server 2003 based production environment. We are currently facing an issue where the memory usage of machine slowly keeps on going higher and higher eventually resulting in “Memory Allocation Failure” to tuxedo servers. We then have to do a complete restart of tuxedo which stabilizes the system for other few days.
    We have been analyzing the our source code in development/test environment using different tools like a customized Alzheimer tool and IBM purify but both tools reported no memory leaks. We then developed a test tuxedo server exposing a tuxedo service which simply allocates a memory to a response buffer and then returns the response buffer. I then configured tuxedo queue with same name “MEMTEST3” and configured a TMQForward server to call this “MEMTEST3” service every time a message is en-queued to the MEMTEST3 queue.
    unsigned long _LIBENTRY ulTPAlloc(FBFR32 **ppc, long size)
    unsigned long ulRes = MSG_SUCCESS_c;
    ppc = (FBFR32 ) tpalloc("FML32", (char *) 0, size);
    if (*ppc == (FBFR32 *) 0) {
    vLogMessage(hGetLogHandle(), MSG_MEM_ALLOC_ERR_c, (char *) 0, (Event_t *) 0,
    BM_NOSUPPRESS_c, size);
    ulRes = MSG_MEM_ALLOC_ERR_c;
    return (ulRes);
    /*==============================================================================
    Service MEMTEST2
    ==============================================================================*/
    void MEMTEST3(TPSVCINFO *pRequest)
    FBFR32 *pFmlResponse = NULL;
    FBFR32 *pFml = NULL;
    unsigned long ulRes = MSG_SUCCESS_c;
    unsigned long ulActionCode = 0;
    int iExitValue = 0;
    long lTpurcode = 0;
    FBFR32 *pFmlNULL = NULL;
    userlog("Starting MEMTEST3 service.");
    if (pRequest == NULL || pRequest->data == NULL)
    vLogMessage(hGetLogHandle(), MSG_API_ARGS_ERR_c, NULL, NULL, BM_NOSUPPRESS_c);
    ulRes = MSG_API_ARGS_ERR_c;
    else
    pFml = (FBFR32 *) pRequest->data;
    userlog("MEMTEST3: GET THE MEM");
    ulRes = ulTPAlloc(&pFmlResponse, 1024);
    userlog("Ending MEMTEST3 service.");
    tpreturn( iExitValue, lTpurcode, ( char * ) pFmlResponse , 0L, 0L );
    While I was en-queuing the messages to the queue, I kept on monitoring the memory usage of the server hosting the service. What I observed was that I saw an initial hike in the usage of memory of the server followed by small jumps in memory increase. I kept on monitoring the server for a long time and the memory was never returned. What I suspect is that there is memory leak in tuxedo TMQforward process as it never released the memory allocated in the service.
    Can anyone help how this situation can be avoided ?
    Kind Regards,
    Asim

    Hi Todd,
    Also as well as my previous question, I also found your reply to another user posting something similar at Re: Memory leaks in Tuxedo libraries
    You mention that:
    In general Tuxedo will free anything it allocates, although there are cases where memory is allocated and not freed because:
    +1) it is one time or a fixed number of times allocations that will not continue to grow, and freeing up the memory just before exiting isn't of any benefit.+
    +2) the memory is under Tuxedo's memory management functions where we manage our own look aside lists to provide better buffer allocation performance and again freeing these before process termination is of little benefit.+
    Our code does only issue TPALLOC once and then a TPRETURN - could point (1) of your comment above also be something of concern to us, where we would observe a continuous growth of memory usage?
    I know it may sound like a stupid question but do we need to run our code 20,000 times before memory gets freed?
    Kind Regards,
    Asim

  • Memory Leak in Flex Builder

    I created Services.mxml in the tutorial, set it as the
    default application file, and dragged the first component onto the
    design view screen, a label, when Flex Builder seems to get
    sluggish. Jumping out to the task manager revealed javaw.exe
    rapidly accumulating memory usage, heading for 300,000 K. I killed
    FB before it hung the machine and restarted it.
    I was able to replicate it by being in a hurry. I created
    another Services2.mxml as an application, and while it was Building
    the workspace i tried to drag a Label onto the stage. Twice. The
    cursor didn't change, but they eventually they appeared. Checking
    the task manager revealed that i had put javaw.exe again in a
    tailspin, rapidly accumulating memory usage.

    I'm also experiencing huge memory leaks from beta 3...after a
    couple of builds memory allocation for javaw is around
    300MB...hopefully this will get fixed. thanks,
    -george

  • Memory leaks during child window close

    Hi All,
       We have a tool that generates code for WPF application. In one of the applications WPF main window displays a child window in the form of a tab. The main window here can hold multiple child windows. I did a small test. I opened main window and
    took memory snapshot with the help of .Net memory profiler. Opened child window and closed it immediately. I took snapshot again and compared with the previous one. To my surprise , many new objects/collections have been active in the heap and due to this
    memory consumption got increased almost exponentially.  If I open and close more and more child windows then memory consumption is keep on increasing.
    During child window close , I am performing all the clean up like clearing all collections , hashmaps etc. As per the suggestions mentioned in forums , I am taking care of cleaning up all the members data like DispatcherTimer , unregistering event handlers
    etc. But still memory is not being freed up even after closing the child window. As per the profiler output most of the memory has been occupied by Hashtable , Hastable.bucket[]. Profiler even reported few pinned instances as well but it looks everything is
    evident from framework API not from my code. I could see styles, controltemplates , System resources etc as active and reachable objects.
    I am just wondering am I getting affected by framework flaws or could there be anything I can do in my source to get rid of this memory leak. Request your comment and appreciate your help on this.
    Thanks,
    Brahmaji.

    Hi ,
     Thanks for the response. Basically I first opened parent panel which is of type Window. It included menu , toolbar etc. For menu/toolbar events it opens child windows which gets displayed in main window in the form of tabs. This is my use case.
    I tried the suggested profiler Redgate Ants profiler. Its very good and informative! I ran the profiler
    got the following output. Though I closed the child window it seems objects are still there in memory . No where I left out string , byte array objects in my code.
    Not sure why Runtimemethodinfo , hastable bucket are there in memory. I even tried the workaround mentioned at here.
    I thought panel resources might have not been freed up and in my code I am clearing them as well. Still did not see much improvement. Any additional things do I need to check? Please let me know.
    Thanks,
    Brahmaji.

  • 5.0.2 still MEMORY LEAKS with Java on multiple tabs/windows

    same problem with last update.
    Memory Leaks (upto 2.5 GB) when Java applets load
    in multiple windows/tab.
    Someone also have this problem?
    My other post prior of last update:
    http://discussions.apple.com/message.jspa?messageID=12204453#12204453
    Message was edited by: fascox

    If you want to report this issue to Apple's engineering, send a bug report or an enhancement request via its Bug Reporter system. To do this, join the Mac Developer Program—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report or enhancement request. The nice thing with this procedure is that you get a response and a follow-up number; thus, starting a dialog with engineering.

  • Media Encoder is a memory leak - windows

    Applies to: Version 5.5.1.12 - 64 bit, Windows (Most likely earlier versions too)
    Reproducing the problem:
    Start Media Encoder as a standalone application by double clicking the icon.
    Close the window (by clicking the 'x' in the top-right corner) of Media Encoder.
    It does just that: closes the window. It does not close the process.
    The process now has no window-handle, thus the user can not access it.
    When user starts the application again, another process is created.
    Thus the previous process becomes a memory leak.
    Workaround:
    Open Windows Task Manager by pressing Ctrl-Alt-Del keys simultaniously then selecting Task Manager
    Click the 'Processes' tab
    Highlight 'Adobe Media Encoder.exe'
    Click 'End Process'
    Ignore the warning and kill the process

    Bill, Sometimes it takes AME and related components up to 30 seconds to close various processes.  If you close the app and immediately start a new instance, the old process sees that AME is still running and may not shut down it's process until you shut down your computer.  So give it a little time after shutdown to see if that helps.  That said, there are situations that I have seen myself that AME would not close all processes in background.  In many of those cases, it had to do with dynamic link and what type of files or assets you opend up and what application launches AME.  Sometimes when AME is launched by other applications like Premiere Pro, it leaves a process alive in case PPro is using it. but if you close all Adobe apps, it should close your process as well. Over the past few cycles, we have worked on improving processes. Let me know if the above info doesn't help.

Maybe you are looking for

  • How can i recover all my data from my HDD?

    My main External Hdd while writing to it got an error saying Cyclic Redundancy I tried using Chkdsk but it states that the data had turned RAW. Upon restarting my pc the disk drive H was no longer visible and the Hdd space is now unallocated space. 

  • Accounting Effect for Capital Goods Purchase

    Hi, Iam using SAP 8.8 PL 13. How does the accounting takes place in case of an Item marked as Fixed Asset in Item Master? In GL account determination I have assigned Capital Cenvat Credit  A/c. for Capital Goods on Hold A/c. Suppose I purchase an Fix

  • Garbage characters when using CR XI R1 with Sharp M350 printer PCL5e driver

    My application uses CR XI R1. We have a customer who has a Sharp M350 printer. When printing or previewing a report from my application with this printer set as the default, the text is garbled - the characters look like gibberish. If they change the

  • [PARTIALLY SOLVED] Arch on MacBook4: can't install GRUB

    I've been running Arch on my MacBook4 (4 years old now) for quite some time in dualboot mode and have already set up GRUB sucessfully several times. I therefore feel kinda bad that I have to open a new thread this time, but after wasting the whole mo

  • TS4123 Every time I try and sync my iPhone my laptop shuts down.

    I have tried reinstalling iTunes. I have reset all contents and setting on the iPhone. I tried downloading my tracks as a playlist. I have about 1000 songs on iTunes and at the last attempt it only synced 250 before shutting down. I have tried everyt