[issue41587] Potential memory leak while using shared memory

李超然 added the comment: Thank you Tim Peters for replying to me. I tried your demo and it is a proof exactly I want. It did prove that there is no memory issue. And I tried to modify my own code and showed the same result. I will close this issue. -- resolution: -> not a bug stage: -

[issue41587] Potential memory leak while using shared memory

Tim Peters added the comment: There's no evidence of a Python issue here, so I recommend closing this. It's not the Python bug tracker's job to try to make sense of platform-specific reporting tools, which, as already explained, can display exceedingly confusing numbers. We (the Python proje

[issue41587] Potential memory leak while using shared memory

Eric V. Smith added the comment: Okay. We'll see if someone else can provide more info. -- ___ Python tracker ___ ___ Python-bugs-l

[issue41587] Potential memory leak while using shared memory

李超然 added the comment: Sorry, I don't know what I can do about it. In my perspective, I think there is a memory leak because monitor software have provided proof for me to believe that. I have provided a script to reproduce this issue. I think that is enough for developers to conduct other t

[issue41587] Potential memory leak while using shared memory

Eric V. Smith added the comment: Sorry, I don't have any particular suggestion other than accounting for all virtual, shared, and physical memory of all types, and seeing how they're being used and allocated per-process by the various tools. There are probably guides for this on the internet

[issue41587] Potential memory leak while using shared memory

李超然 added the comment: Okay. I know this is complicated. So how can I make sure this is not an issue? Can you provide some steps or a bash script to prove that the memory increment issue does not exist? I'm now not being persuaded because I don't know how to prove there is no issue about the

[issue41587] Potential memory leak while using shared memory

Eric V. Smith added the comment: You'll have to play with it. I'm just saying that it's a very complicated subject, and not as simple as asking how much memory an individual process is using. For example, see https://www.howtogeek.com/659529/how-to-check-memory-usage-from-the-linux-terminal/

[issue41587] Potential memory leak while using shared memory

李超然 added the comment: You mean if I have a machine that has 16GB RAM, and the maximum shared memory size is 8GB. I then create two processes to write to this shared memory, and the system won't run out of memory. Is it right? I can try this experiment later on. But I can not understand this.

[issue41587] Potential memory leak while using shared memory

Eric V. Smith added the comment: It's likely that the same memory is being counted by both processes, to the output is misleading. Shared memory is notoriously difficult to allocate per-process. For example, it's definitely true that the shared memory is consuming virtual address space in bo

[issue41587] Potential memory leak while using shared memory

New submission from 李超然 : We find an issue while using shared memory. When opening another process to overwrite the shared memory, the memory of this process will increase to about the size of this shared memory. So when several processes try to read or write the shared memory, there will be N