[issue31790] double free or corruption (while using smem)

Terry J. Reedy added the comment: pydev core has not touched 2.7 in a year. Anyone else maintaining 2.7 has had a chance to grab 2.7 issues. So all 2.7 issues should be closed unless obviously relevant to current issues (and even then have 2.7 removed). I agree that the later does not

[issue31790] double free or corruption (while using smem)

Irit Katriel added the comment: Terry, this is a 2.7 memory management issue with not a log to go by. Would you agree that there is no chance we can do anything about this? -- nosy: +iritkatriel status: open -> pending ___ Python tracker

[issue31790] double free or corruption (while using smem)

Zoltan Krajcsovics added the comment: In a span of about 1 month, I had multiple errors: *** Error in `/usr/bin/python': free(): invalid next size (normal): 0x55f9c9e7c970 *** *** Error in `/usr/bin/python': free(): invalid next size (normal): 0x55e33fda3970 ***

[issue31790] double free or corruption (while using smem)

Terry J. Reedy added the comment: The error log is not present. Try uploading again. -- nosy: +terry.reedy ___ Python tracker ___

[issue31790] double free or corruption (while using smem)

New submission from Zoltan Krajcsovics : Command executed when the crash happened: /usr/bin/python /usr/bin/smem -t -c command pss -P /usr/lib/chromium/chromium The attached error.log contains the backtrace and memory map printed. This is a sporadic error, the command is