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.

Similar Messages

  • [InDesign CS3] how to find the reason of the memory leaks?

    Hi all,
    I'm working with InDesign CS3. I wrote a plug-in and loaded it into InDesign in debug mode. After I closed the application, I got a console window showing memory leaks as following:
    Leaks! 52 leaks, 716804 bytes
    Press any key to continue . . .
    Does anybody know how to find the reason of the memory leaks? Thanks a lot!
    Nicole

    Thanks Dave. I'm using Windows, and I also tried MemoryTracker. I got a Leaks.txt which shows the detail of memory leaks as following. But I really can't understand it. Any help? Thanks.<br /><br />Leaks!  7 leaks, 455252 bytes<br /><br />65036 bytes at: 7B22FF8<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01C96DEC     BIBGetVersion cannot be found in any module!<br />     01C96E60     BIBGetVersion cannot be found in any module!<br />     01C979E4     cannot find address in any module!<br />     0131F511     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     0131F4C4     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     00EDBC7E     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     00EDBFBE     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     00EDC558     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     1002C26E     cannot find address in any module!<br />     1002BFB9     cannot find address in any module!<br />     00401644     cannot find address in any module!<br />     00405146     cannot find address in any module!<br />     00404EBD     cannot find address in any module!<br />     7C817067     RegisterWaitForInputIdle cannot be found in any module!<br />65036 bytes at: 7B32E38<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01C96DEC     BIBGetVersion cannot be found in any module!<br />     01BB149B     cannot find address in any module!<br />     01BB4C62     cannot find address in any module!<br />     00EDBCE3     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     00EDBFBE     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     00EDC558     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     1002C26E     cannot find address in any module!<br />     1002BFB9     cannot find address in any module!<br />     00401644     cannot find address in any module!<br />     00405146     cannot find address in any module!<br />     00404EBD     cannot find address in any module!<br />     7C817067     RegisterWaitForInputIdle cannot be found in any module!<br />65036 bytes at: 7B52AB8<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01C96DEC     BIBGetVersion cannot be found in any module!<br />     02331A7A     cannot find address in any module!<br />     0236E7CD     cannot find address in any module!<br />     43726F6C     cannot find address in any module!<br />65036 bytes at: 7C93D80<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     02331F36     cannot find address in any module!<br />     02367F85     cannot find address in any module!<br />     02415DB4     cannot find address in any module!<br />     3F800000     cannot find address in any module!<br />     02416799     cannot find address in any module!<br />     FFFFFF11     cannot find address in any module!<br />65036 bytes at: 7CD6028<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01CE1C14     cannot find address in any module!<br />     01DD9346     CTGetVersion cannot be found in any module!<br />     01D9B052     CTGetVersion cannot be found in any module!<br />     01D9B189     CTGetVersion cannot be found in any module!<br />     01D9BB21     CTGetVersion cannot be found in any module!<br />     01D9BD0C     CTGetVersion cannot be found in any module!<br />     01D9CE96     CTGetVersion cannot be found in any module!<br />     01D9CEFF     CTGetVersion cannot be found in any module!<br />     01DDBEA2     CTGetVersion cannot be found in any module!<br />     01DDC214     CTGetVersion cannot be found in any module!<br />     01DDC7C6     CTGetVersion cannot be found in any module!<br />65036 bytes at: 16D68200<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01BB178C     cannot find address in any module!<br />     01BCE7C8     cannot find address in any module!<br />     01BCEE13     cannot find address in any module!<br />     01BD28C5     cannot find address in any module!<br />     01BD4CB7     cannot find address in any module!<br />65036 bytes at: 20B68F88<br />     4172627C     MemoryPool::GetNonPoolSizePeak cannot be found in any module!<br />     00EDC1CB     K2Internals::K2VectorBase<HolderPtr<IPMUnknown>,K2Allocator<HolderPtr <IPMUnknown> > >::fill_insert cannot be found in any module!<br />     01C9C74F     cannot find address in any module!<br />     01CE1C14     cannot find address in any module!<br />     01D2F1A1     cannot find address in any module!<br />     01D6F789     CTGetVersion cannot be found in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!<br />     07BFB464     cannot find address in any module!

  • Winverifytrust memory leaks?

    I had a question on winverifytrust's catalog signing. We are using winverifytrust and we don't call WTD_ACTION_STATE_CLOSE after the call, we call it only if hWVTStateData is not NULL. What we see is that system memory consumption continues to rise in spikes
    The consumption rises, then settles down to a steady state and then rises again after some time and then rises again after a longer period with a larger amount. We believe this may be the side-effect of internal caching done by the catalog signature trust
    API. Could someone help confirm the behaviour
    1. Is this expected behaviour?
    2. Is our usage of the API (not calling STATE_ACTION_CLOSE unconditionally correct?)
    3. Does internal caching behave this way, if so does it reach a steady state where the cache size will not grow beyond a certain limit, can that limit be predicted?
    Thanks,
    Balbir

    Hi,
    Could you please have a share for which developer language we are using here?
    Regarding the issue here, we'd better seek help in some developer forum for a better assistance.
    MSDN troubleshooting and support
    http://msdn.microsoft.com/en-hk/hh361695.aspx
    Meanwhile, we might also take a use with the Windows Performance Toolkit to find memory leaks.
    See the blog below:
    Using the Windows Performance Toolkit to find memory leaks
    Windows 7: Memory Leak Troubleshooting
    Please note: Since the websites are not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards
    Michael Shao
    TechNet Community Support

  • 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 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.

  • Windows Audio Device Graph Isolation [audiodg.exe] MEMORY LEAK - EATS OUT 60-85% of CPU

    Hello,
    I've updated, 2 days ago, from Win 8 to Win 8.1 Pro and this memory leak problem that has occurred to me previously in other Win versions has arrived again. Didn't upgrade from boot, just from the desktop. Cleaned up the previous Windows installations and all
    that jazz that was inherent to Windows updates. Tried to fix this problem with the normal method of disabling the enhancements at the playback device but they are gone.
    My drivers are all up to date and have a Conexant SmartAudio HD sound platform. 
    Thanks in advance for any sort of help.

    I maybe got a solution for this... (Worked for me)
    I
    Right-click the speaker icon in the lower right corner.
    Select Playback Devices from the menu. A list of devices should appear on the screen.
    Double-click the device that has a green checkmark. The properties windows for that device should open.
    Click the Enhancements tab at the top.
    From the list of enhancements, uncheck all of them, or click the Disable all enhancements checkbox.
    Click the OK button to save your changes and close the window.
    Click OK to close the Playback Devices window.
    Please reply if that helped you :-)

  • Version 7.3 memory leaks Windows 8 then crashes

    Hello, There are already some threads about this, but they mention Windows 7. I can confirm the memory leak (it gets up to 1.5 gb then crashes) is happening on windows 8 and windows 8.1. This issue wasn't present for skype 7.2.0.103 , it is present for 7.3 and also for 7.4.0.102 . It leaks for about 0.6MB per second , it constantly writes to disk 0.3 MB/S and uses ~12% CPU. This behavior happens only after I'm logged in. No calls, no messages, just staying logged in is sufficient. Furhtermore, the memory leaked by Skype is not returning to the system, so I end up having 75% memory used on a 16 GB machine after restarting skype several times (because it crashes and I need skype to communicate with my contacts constantly). Please provide me with a link to download 7.2 (since it works). I had this issue with Skype 7.3 and in 7.4 nothing got solved, so please give me a link to something that works rather that something that's shiny but broken. Thank you

    The memory leak is still occuring in 7.6.0+.
    Downgraded to 7.2.0.103 and it still does not prevent memory leak. Eventually it crashes around 1100MB of RAM usage on my system. Validated everything is working like directx, etc. I think this is a Microsoft Windows 8.1 bug, and not just a Skype memory leak issue, as I have seen one other application do the exact same thing (grow to 1100MB and crash). Time to go bug Microsoft for a solution... oh wait... Skype is a Microsoft product. 

  • Memory leak playing podcasts in iTunes 11.2, Windows 8.1 x64

    I've already uninstalled and reinstalled iTunes 11.2 64 bit.
    When I play a podcast it plays for a few minutes then iTunes freezes.  Watching it in task manager its obvious there's a memory leak.  Memory climbs steadily until about 1.6Gb when it dies.
    Any suggestions?
    Can we download earlier versions?

    Was hoping 11.2.2 would fix it. Nope, the memory leak is still there in the podcasts tab. The workaround is to refresh podcasts and jump to the music tab.

Maybe you are looking for