Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-19805

MMap memory mapped file address allocation code cannot handle addresses non-aligned to memory mapped granularity size

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 3.0.5, 3.1.6
    • 3.0.6, 3.1.7
    • MMAPv1
    • None
    • Fully Compatible
    • Windows
    • Platform 7 08/10/15

    Description

      As part of the fix to SERVER-10516, the code tries to find the next available free slot of virtual memory to allocate a memory mapped file. If the base address of the memory region or the allocation size returned by Virtual Query are not aligned to the memory mapped file granularity boundary, MongoDB will then try to map a file to an address not aligned with the correct granularity.

      https://github.com/mongodb/mongo/commit/0205239ecb579e20b05cee3a0df394eb11ba14ce

      Attachments

        Issue Links

          Activity

            People

              mark.benvenuto@mongodb.com Mark Benvenuto
              mark.benvenuto@mongodb.com Mark Benvenuto
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: