2018-01-26, 23:15
I've rebuilt LE master/Kodi master with
The following image shows the end of the 2nd and 3rd play of Elysium:
where there is a deficit of 47MB after the second play, which falls to 23MB after the 3rd play.
After 5 full plays of Elysium the deficit is still only 64MB
However after a 6th play, the deficit increased to 108MB.
But after a 7th play, it reduced to 78MB.
This is more like #0804 than #0805 - there is a small leak, but it's not as significant as I saw with #0805.
But it's weird, as the gcc/glibc changes are in #0806, and #0805 showed a significant deficit after each play (even though it also used gcc-6.2.0), so I'm not sure why switching back to gcc-6.2.0/glibc-2.25 would restore the significant losses seen with #0805. Or it's another red herring, and the issue is just with #0805. That said, I have just tested a master build which is using gcc-7.3.0 and the deficit increased rapidly - first play 94MB, second play 181MB - so perhaps there is a gcc-7.x bug that is causing this increased level of leakage.
I can upload these gcc-6.2.0/gcc-7.3.0 test builds if this will be useful.
gcc-6.2.0
and glibc-2.25
and the results initially look similar to #0804, with reduced leakage compared with #0805.The following image shows the end of the 2nd and 3rd play of Elysium:
where there is a deficit of 47MB after the second play, which falls to 23MB after the 3rd play.
After 5 full plays of Elysium the deficit is still only 64MB
However after a 6th play, the deficit increased to 108MB.
But after a 7th play, it reduced to 78MB.
This is more like #0804 than #0805 - there is a small leak, but it's not as significant as I saw with #0805.
But it's weird, as the gcc/glibc changes are in #0806, and #0805 showed a significant deficit after each play (even though it also used gcc-6.2.0), so I'm not sure why switching back to gcc-6.2.0/glibc-2.25 would restore the significant losses seen with #0805. Or it's another red herring, and the issue is just with #0805. That said, I have just tested a master build which is using gcc-7.3.0 and the deficit increased rapidly - first play 94MB, second play 181MB - so perhaps there is a gcc-7.x bug that is causing this increased level of leakage.
I can upload these gcc-6.2.0/gcc-7.3.0 test builds if this will be useful.