Hmm… I’ll definitely try the workarounds in this post, but if 1.6 is supposed to have resolved it, my issue may be different. The 1.6.0.dev20200625+cpu nightly leaked in my above allocation test.
Do you know if the fix for the issue you linked would have been in by then? It’s the latest 1.6 nightly I could find.