Skip to content

MemoryMappedView leak #133744

Open

Description

@jkotas

A few more findings from the same 64KiB-page machine, separate from the thunk and GC bitmap-accounting issues above:

  1. Empty memory-mapped views leak one OS-page mapping on Unix. CreateView maps one byte for an empty view but records a native length of zero. Disposal then calls munmap(address, 0), which fails. Reproduced against the locally built libraries: all 32 disposed empty views remained mapped. This isn't exclusive to 64KiB pages, but the leaked virtual mapping is 64KiB per view here, rather than 4KiB.

Originally posted by @EgorBo in #133675

Activity

  1. added and removed
    untriagedNew issue has not been triaged by the area owner
    on Sep 11, 2026
  2. dotnet-policy-service commented on Sep 11, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/area-system-io
    See info in area-owners.md if you want to be subscribed.

  3. added this to the 12.0.0 milestone on Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions