Slashdot Mirror


Vista Runs Out of Memory While Copying Files

ta bu shi da yu writes "It appears that, incredibly, Vista can run out of memory while copying files. ZDNet is reporting that not only does it run out of memory after copying 16,400+ files, but that 'often there is little indication that file copy operations haven't completed correctly.' Apparently a fix was scheduled for SP1 but didn't make it; there is a hotfix that you must request."

6 of 661 comments (clear)

  1. Re:Actual info... by Phil246 · · Score: 5, Informative
    actually, fta:

    Although the problem occurs where users are running Kaspersky security products, it's a kernel leak that lies at the root of problem (the problem's not confined to systems running Kaspersky software, that just that this application seems to exacerbate the issue).
  2. Re:Billy G says by Seismologist · · Score: 5, Informative
    Found the quote on wikiquote:

    I laid out memory so the bottom 640K was general purpose RAM and the upper 384 I reserved for video and ROM, and things like that. That is why they talk about the 640K limit. It is actually a limit, not of the software, in any way, shape, or form, it is the limit of the microprocessor. That thing generates addresses, 20-bits addresses, that only can address a megabyte of memory. And, therefore, all the applications are tied to that limit. It was ten times what we had before. But to my surprise, we ran out of that address base for applications within--oh five or six years people were complaining.
    --
    ~ In Trust, We Trust ~
  3. OLE mem leak; only affects 'extended attrib' files by I'm+Don+Giovanni · · Score: 5, Informative
    According to the cited "hotfix" link, http://support.microsoft.com/kb/942435/en-us , the problem is due to an OLE memory link when dealing with files that have "extended attributes".

    This problem occurs if the following conditions are true:
      * The files include extended attributes.
      * You copy lots of files in a single operation.

    CAUSE
    This problem occurs because of a memory leak in the Windows OLE component. This memory leak is triggered by the way that Windows Explorer deals with the extended attributes of the files.

    --
    -- "I never gave these stories much credence." - HAL 9000
  4. Re:Actual info... by Anonymous Coward · · Score: 5, Informative

    Actually, the bug is in the shell, not the kernel and only files with altnerate data streams trigger the leak. The KB article that Adrian links to states that very clearly, but he's been on an anti-Windows rampage lately that's blinded him to the facts.

    Very few files have data streams, so the vast majority of users won't ever see a problem. Kaspersky choses to pollute every single file with a stream, however, which is why systems with it installed exhibit the problem.

  5. Bad summery by gravis777 · · Score: 5, Informative
    Apparently the submitter skimmed the article, and decided to post up a Vista bash on Slashdot.

    FTA:

    The "Out of Memory" error (which is affectionately known at the PC Doc HQ as the "Out of Cheese" error ... don't ask why ...) is one of the biggest and most baffling of Vista's file handling problems has been occurs when a Vista user (running Kaspersky Anti Virus 6 or 7) tries to copy a large number of files (~16,400) Apparently its just a problem with this antivirus program running in Vista. I move large amounts of files around in Vista quite often (granted, its Vista 64), sometimes well over 20,000 files at a time, and have never run into this issue.
    1. Re:Bad summery by Zebra_X · · Score: 5, Informative

      Lol the TFA is FUD. Read the HOTFIX notes which explains that the issue is with Windows OLE (NOT part of the kernel) and files that utilize extended attributes. Note that the crappy AV product adds extended attributes to all of your files (which i'm sure speeds up every file operation on your PC), thus with a kapersky infected computer - you are assured to have the problem. With "normal" files it's unlikely you will have this issue. Media files and the new office files are more likely to pose a problem than your standard files.

      The article does not state clearly wether physical memory is a constraint.