On Fri, Aug 14, 2020 at 2:24 PM Pip Cet wrote: > If no, any ideas on how to fix it? The obvious fix would be to always > mark all pdumped objects, but that has a performance cost. Less > obvious would be clearing the memory in the pdumper image that belongs > to an object that's being "freed", or keeping track of which pdumper > objects are still valid after GC... I've gone with the last idea. This patch should fix things, though given how difficult the bug is to trigger reliably it might also merely appear to fix it...