XtraDB don't start if innodb_buffer_pool_size>19G (Windows)

[Emk]

On Intel server (24 core, 48Gb) under Win 2008 I have error when set innodb_buffer_pool_size=20G:
InnoDB: VirtualAlloc(0 bytes) failed; Windows error 87
InnoDB: Fatal error: cannot allocate the memory for the buffer pool

In "std" InnoDB all work fine with innodb_buffer_pool_size>19G.

[Yasufumi Kinoshita (yasufumi-kinoshita)]

It may be InnoDB-Plugin's bug.

Did you test 16G, 12G, 8G, 4G also?
And did 19G work fine? (Did 19G really allocated? Was it 3G?)

"InnoDB: VirtualAlloc(0 bytes) failed; Windows error 87",
"0 bytes" means size == 0 at
os/os0proc.c: 132
 size = *n = ut_2pow_round(*n + (system_info.dwPageSize - 1),
      system_info.dwPageSize);

I don't have Windows-64bit env. So the following is just a estimation.

I suspect system_info.dwPageSize may be 32bit in Windows.
If so, we may need to change it to
 size = *n = ut_2pow_round(*n + ((ulint)system_info.dwPageSize - 1),
      (ulint)system_info.dwPageSize);

Sorry, I cannot confirm it for now.

[Emk (emk)]

I test only 19G and 20G.
Now I understand that really allocated is 3G.
Can I use os0proc.c from std InnoDB, not from XtraDB, is it compatible with XtraDB?
I test idea about 32bit system_info.dwPageSize this evening.
Sorry my english.

[Stewart Smith (stewart)]

All development of XtraDB has moved under the Percona Server project - https://launchpad.net/percona-server - If this bug can be reproduced against current Percona Server, please file this bug against percona-server (you can simply do so by using the "Also affects project" link above).

Thanks,
Stewart Smith
Director of Server Development
Percona.