Windows 7 RTM contains what appears to be a memory leak bug that occurs when the chkdsk /R command is initiated on a non-system volume. The result is the process taking up as memory as possible until the system is using over 90% of your total memory. The memory usage issue occurs when chkdsk /R is initiated in the command prompt and in the GUI, in which case it would be under the explorer.exe process. The memory usage issue can also be replicated in Windows Server 2008 R2.

Chkdsk Stage 4 of 5 at 82% completion. A total of 7.82GB out of 8GB of RAM was being used.
Some fans have been calling this a “showstopper” bug. Randall Kennedy from Infoworld even goes as far as to suggesting that this “bug” could derail the launch.
However, ZDNet’s Ed Bott claims this bug is nothing close to a showstopper. A few tries at replicating the issue on different test systems showed that Microsoft gives several warnings prompting the user to dismount the volume or perform the check at a scheduled time the next time you reboot before Windows starts up.
Steven Sinfosky, president of the Windows division at Microsoft, left a comment on Chris123NT regarding this issue. He says that this is indeed not a showstopper and occurs by design.
In this case, we haven’t reproduced the crash and we’re not seeing any crashes with chkdsk on teh stack reported in any measurable number that we could find. We had one beta report on the memory usage, but that was resolved by design since we actually did design it to use more memory. But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory. Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.
While we appreciate the drama of “critical bug” and then the pickup of “showstopper” that I’ve seen, we might take a step back and realize that this might not have that defcon level. Bugs that are so severe as to require immediate patches and attention would have to have no workarounds and would generally be such that a large set of people would run across them in the normal course of using their PC.
Sinofsky also stated that they are doing overnight stress testing of 40 machines to see if the problem can be reproduced.
Related posts:
I managed to get a hold of Steven Sinofsky on the Windows Engineering Blog. What he told me was that this was by design. He wanted chkdsk /r to be a fast process and said it was normal for a lot of RAM to be used up. He also told me if I had to run it in Windows, it would be best to leave the machine alone. And besides, how many times would you actually do a chkdsk /r on a secondary disk? I certainly hope not every day, if so, then you might need a new hard drive. I have seen my memory usage go up to about 97 percent but I have not gone to the point of BSoDing as some other people have claimed they did.
Whoops, guess I just restated the article above. But yeah, just to confirm, Steven Sinofsky did tell me the same thing he told the public.
[...] http://windows7center.com/news/windows-7-rtm-chkdsk-memory-leak-isnt-a-showstopper/ [...]
Thanks! Good news
Thanks!
Not entirely what I had been trying to find but it was some good reading anyway, guess its a ok that I wasn’t able to search properly or I wouldn’t have found this.
Found myselfself here searching for something entirely else, but turned out to be a cool read anyway, so I guess sometimes it’s ok that you can’t use a search engine properly.
автор признайтесь писали после алк?)
Interesting post – I was thinking about an article on a related subject that I need to take a shot at, but from a slightly different angle. Thank you for sharing this with us…Obviously a lot of people appreciate it too!
[...] [...]
Забавно.