Lazy OccName field in Name leaves potential for leaks
The OccName field in Name has been strict since ccaf7b66
Since 72c0e078 the field is now lazy, but no mitigation was taken in that patch to avoid the kind of leaks alluded to in 2001.
Hence, when using ghc-debug I could see thunks in the Name field which were retaining things. I think we should revert 72c0e078 until it can be verified that this change doesn't introduce retainer leaks.
Name's are very long lived (in the NameCache) so it's important they do not cause leaks like this.