Skip to content

memory overcommit in Linux process yields BSOD #123

Closed
Closed
memory overcommit in Linux process yields BSOD#123

Description

@tycho
Steven Noonan (tycho)
opened on Apr 11, 2016

I ran Stream with a 32GB dataset size on a machine with 16GB of RAM, and hit a bugcheck:

Microsoft (R) Windows Debugger Version 10.0.14281.933 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

  @russalex edit:  removing the dump content

Activity

  1. jernejs commented on Apr 11, 2016

    @jernejs
    Jernej Simončič (jernejs)
    on Apr 11, 2016

    I tried the classic bash forkbomb :() { :|: & }; :, and got FAULTY_HARDWARE_CORRUPTED_PAGE once and IRQL_NOT_LESS_OR_EQUAL another time.

  2. patryk9200 commented on Apr 11, 2016

    @patryk9200
    Patryk Golus (patryk9200)
    on Apr 11, 2016

    I run into similar behavior BSOD
    IRQL_NOT_LESS_OR_EQUAL
    when running apt upgrade

  3. jernejs commented on Apr 11, 2016

    @jernejs
    Jernej Simončič (jernejs)
    on Apr 11, 2016

    Here's the forkbomb result.

  4. benhillis commented on May 27, 2016

    @benhillis
    Ben Hillis (benhillis)
    on May 27, 2016
    Member

    We've mitigated the forkbomb issue and that change will be in an Insider build soon.

  5. bitcrazed commented on Sep 28, 2016

    @bitcrazed
    Rich Turner (bitcrazed)
    on Sep 28, 2016
    Contributor

    Should now be fixed.

  6. Rich Turner (bitcrazed)
    closed this as completedon Sep 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions