Improve Window secure allocator

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.4, 4.1.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Security 2018-09-24, Security 2018-10-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On Windows 10 and 2012 R2,the parameter dwMaximumWorkingSetSize of SetProcessWorkingSetSizeEx must be >= (dwMinimumWorkingSetSize + 0x7000). The 0x7000 appears to be undocumented and discovered during adhoc testing.

      This can be triggered by secure memory exhaustion on Windows. In 4.0, the Encrypted Storage Engine uses more secure memory per database which means it is likely to encounter this.

            Assignee:
            Mark Benvenuto
            Reporter:
            Mark Benvenuto
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: