pshm memory leak on windows platform

[leekunpeng]

When using p_shm_new to open shared memory in different programs and allocate different sizes, pshm is always the size of the first allocation, and memory leaks will occur when applying for allocation again.
In particular, if the first application is large enough, the second application of small memory will not report an error. On the contrary, if the first application is small, the second application of large memory will cause a memory leak.

[leekunpeng]

@saprykin Hi~ Alexander. Sorry for border you, could you please check this error? extremely grateful

[saprykin]

Hi, yes let's take a look on this issue :) Do you have a working (reproducible) example of the issue? How do you detect memory leak?

[leekunpeng]

Hi, yes let's take a look on this issue :) Do you have a working (reproducible) example of the issue? How do you detect memory leak?

Sorry for delay.
Okay, here is an example. I used the p_shm_new function in two programs to open shared memory with the same name but different sizes, and it always succeeds. My question is: In plibsys, is shared memory uniquely identified by both name and size?