Comment 1 for bug 1625774

I can reproduce both the leak and the error destroying models for this. I've added an endpoint to the introspection worker to produce a heap dump so I can work out what it is that's being leaked. The tooling in this area of Go is a bit rough - I'm trying to use the hview tool linked to from this thread https://github.com/golang/go/issues/16410.

It doesn't work with Go 1.7 yet - I tried hacking it to ignore the version reported in the dump, but got errors about unrecognised record kind 101, so I'm trying again with a binary built with Go 1.6.