[issue46849] Memory problems detected using Valgrind

tongxiaoge added the comment: Ok, thanks. There is no memory problem exposed when I add --suppressions=Misc/valgrind-python.supp. I will close this issue. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue46849] Memory problems detected using Valgrind

Change by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46849] Memory problems detected using Valgrind

Christian Heimes added the comment: Valgrind does not understand Python's custom obmalloc allocator. You have to run valgrind with our suppression rules Misc/valgrind-python.supp to ignore false errors. -- nosy: +christian.heimes ___ Python

[issue46849] Memory problems detected using Valgrind

Change by Christian Heimes : -- Removed message: https://bugs.python.org/msg414097 ___ Python tracker ___ ___ Python-bugs-list

[issue46849] Memory problems detected using Valgrind

Terry J. Reedy added the comment: Posting a thousand line message makes following a discussion extremely difficult. Move it into an attachment, if you did not do that already, and delete the message by 'editing' it. As I said, I cannot otherwise respond to this. --

[issue46849] Memory problems detected using Valgrind

tongxiaoge added the comment: I also installed Python3.7.9、Python3. 8.5 tested and found no problems. -- ___ Python tracker ___ ___

[issue46849] Memory problems detected using Valgrind

tongxiaoge added the comment: The latest version is also problematic (Python 3.11.0a5). The above is the output stack information. Here are the steps to reproduce: 1. iotop -b -n 10 & 2. valgrind --leak-check=full /usr/sbin/iotop -b -n 5 > iotop_ test -- Added file:

[issue46849] Memory problems detected using Valgrind

Terry J. Reedy added the comment: It is possible that some core developer may get regular valgrind reports, but I would not know who. I am pretty sure that you should run it at least on the latest release of the 'main' branch, 3.11.0a5, and perhaps even better, the current tip. There

[issue46849] Memory problems detected using Valgrind

New submission from tongxiaoge : Reproduction steps: 1. Execute command: iotop -b -n 10 & 2. Execute the command in another session: valgrind /usr/sbin/iotop -b -n 5 > iotop_test The output information is as follows: [root@openEuler ~]# valgrind /usr/sbin/iotop -b -n 5 > iotop_test ==13750==