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 called every second 0-24, and I got one such error after half a day of running. I probably had another after a few days, but I failed to save that one, so I am not sure, if they are really the same.

It would seem that using a more overloaded / older machine triggers the error more often, the machine I got it on was a

Hewlett-Packard HP Compaq dc7900 Small Form Factor/3031h, BIOS 786G1 v01.27 10/22/2015

The problem seems to have emerged after updating to Debian Stretch.

python version:
Python 2.7.13

smem version:
pool/main/s/smem/smem_1.4-2_all.deb
(could not get an internal smem version, only the debian package)

The error log is not present.  Try uploading again.

In a span of about 1 month, I had multiple errors:

*** Error in `/usr/bin/python': free(): invalid next size (normal): 0x000055f9c9e7c970 ***
*** Error in `/usr/bin/python': free(): invalid next size (normal): 0x000055e33fda3970 ***
*** Error in `/usr/bin/python': free(): invalid next size (normal): 0x0000564d42335970 ***
*** Error in `/usr/bin/python': double free or corruption (out): 0x0000561d8b9d4f80 ***
*** Error in `/usr/bin/python': double free or corruption (out): 0x0000557700e74f80 ***
*** Error in `/usr/bin/python': free(): invalid next size (normal): 0x0000564b6142e970 ***

In the same time-period, I have been running the same code on another system, with a different python version, which did not produce any error:

python version that causes issues:
python --version
Python 2.7.13

python version that is error-free:
Python 2.7.9

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?

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 apply here.