[Milhouse]

Does the leak seem to be once per play? i.e. if you play/stop after a few seconds repeatedly does memory exhaust much faster than playing a single file that lasts an hour? (I'd guess it probably would)

I tested #0805 again, playing/stopping Elysium after about 5 seconds, and the leak seems to be quite small - 11 plays and the RAM deficit is only 48MB (compared with 120MB+ after 2 complete plays), so the leak seems to occur during/throughout playback, possibly the 1-2MB/s allocations are not being released at the end of playback?

How hard would it be to build head of tree with older gcc/glibc? Does that crash with out-of-memory after repeated plays?
(I suspect that #0805 is really the culprit, but the evidence is currently a bit unclear).
BTW John is on holiday this week so we won't get an immediate fix, but would be nice to be sure the bug is in the hevc code when he returns.

I'm currently building latest LE master/Kodi master with gcc-6.2.0/glibc 2.25 (rather than gcc-7.1.0/glibc-2.26) however a lot of other packages were also updated to work with gcc-7.x so rolling back just gcc/glibc might not be a success (and several of the updates packages have received subsequent updated so rolling back the entire PR is tricky). Anyway... I'll let you know.