1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Ooops - Critical Bug

Discussion in 'Windows 7' started by Steve R Jones, 2009/08/07.

  1. 2009/08/07
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
  2. 2009/08/08
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    Found it on my copy of the RC - and it'll **** your memory up at an impressive rate!

    FWIW - the bug is in running chkdsk /r on another drive. If you want to try this, open up the Performance tab of Task Manager and watch it leak. Close the Command Prompt window (where chkdsk /r X: is running) before all your memory is sucked up.
     

  3. to hide this advert.

  4. 2009/08/10
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Why am I not surprised something like this wasn't 'caught'?

    One wonders what else will come to light once Win7 systems will start shipping...
     
    Arie,
    #3
  5. 2009/08/10
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    I think the bug only affects certain chipsets..And as a member on another site pointed out:

    And he kind of has a point;)
     
  6. 2009/08/10
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Yea, sure... despite that Microsoft always claims "we will ship when the product is ready ", fact is that products ship on a date schedule, ready or not.

    The point I want to make is that this doesn't seem like an obscure bug, and allowing for proper testing time should have uncovered it.

    Unfortunately MS already deleted the 'feedback' database for beta testers, so I couldn't see if this had been reported before RTM.
     
    Arie,
    #5
  7. 2009/08/10
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    FWIW - Microsoft doesn't feel that this is a critical issue (from the reading that I've done).

    I can somewhat agree with this - as there's no damage done when it crashes and the only result is that I'm deprived of chkdsk /r on any drive other than my OS partition (it doesn't crash on chkdsk /f or on plain old chkdsk on my system).

    Yes, it's a genuine PITA to get this error - especially since I rarely (if ever) use chkdsk /r on another drive. But it doesn't apply to a lot of systems (those with only one drive), and to multiple drive systems that never have chkdsk /r run on the other drive(s).

    I'm sure that a patch will be issued shortly - and it means that we're on the path for Service Pack 1 already.
     
  8. 2009/08/12
    Lukeno1

    Lukeno1 Well-Known Member

    Joined:
    2009/02/06
    Messages:
    482
    Likes Received:
    0
    The path to SP1 started the day Microsoft started programming it. :p
     
  9. 2009/08/26
    Athlonite

    Athlonite Inactive

    Joined:
    2009/08/23
    Messages:
    174
    Likes Received:
    7
    Actually it's not a bug it's a design feature to allow chkdsk.exe to do its job quicker by caching the files it scans to memory, rather than just reading them from disk LOL... Might have been a great feature if it actually worked, but a 1~1.5min reduction on a 4hr scan time isn't worth the memory foot print it creates. :p
     
    Last edited: 2009/08/26
  10. 2009/08/26
    Lukeno1

    Lukeno1 Well-Known Member

    Joined:
    2009/02/06
    Messages:
    482
    Likes Received:
    0
    Well, once I eventually worked out what you'd written (no punctuation or capital letters in the right places), I disagree. It is a bug because only one chkdsk command actually causes this to happen.
     
  11. 2009/08/26
    Athlonite

    Athlonite Inactive

    Joined:
    2009/08/23
    Messages:
    174
    Likes Received:
    7
    @Usasma I've never had it crash but i do get the larger than usual memory foot print
     
  12. 2009/08/27
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Today I'm trying it.... it did grab 93% of my (12GB) RAM, but is still running after about an hour, so I don't expect it to crash ;)
     
  13. 2009/08/27
    Lukeno1

    Lukeno1 Well-Known Member

    Joined:
    2009/02/06
    Messages:
    482
    Likes Received:
    0
    That's still a heck of a lot of RAM to eat :D
     
  14. 2009/08/27
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well... I'd say "so what "? RAM is there to be used. Not that I think it makes much difference. I didn't keep time, but I think chkdsk /f on my 465GB SATA 2 drive took around 90 minutes.

    At one point I noticed 96% of my RAM being used. Once it finished my RAM was released, and I'm 'back to normal'...
     
  15. 2009/08/27
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    I haven't tried it since that first day - I wonder if there's been a patch released?
     
  16. 2009/08/27
    Lukeno1

    Lukeno1 Well-Known Member

    Joined:
    2009/02/06
    Messages:
    482
    Likes Received:
    0
    I've not tried Win7, as I didn't have 80 years to wait for my 3/4 mb internet to download the huge file :D
     
  17. 2009/08/28
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    I doubt it. At least nothing related listed in WU.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.