https://bugs.documentfoundation.org/show_bug.cgi?id=100244
--- Comment #26 from Dave Gilbert <[email protected]> --- Note 1: Changing almost anything makes this leak go away for me - e.g. adding or removing a field to the pivot table. Note 2: I managed to get this to run in memcheck, but it hasn't found much useful, it doesn't look like most of it is leaked at the end: ==572040== HEAP SUMMARY: ==572040== in use at exit: 3,187,666 bytes in 26,266 blocks ==572040== total heap usage: 47,533,605 allocs, 47,507,339 frees, 5,420,734,732 bytes allocated ==572040== ==572040== LEAK SUMMARY: ==572040== definitely lost: 3,072 bytes in 9 blocks ==572040== indirectly lost: 364,654 bytes in 7,549 blocks ==572040== possibly lost: 32 bytes in 1 blocks ==572040== still reachable: 2,812,860 bytes in 18,683 blocks ==572040== of which reachable via heuristic: ==572040== newarray : 362,368 bytes in 3 blocks ==572040== multipleinheritance: 304 bytes in 2 blocks ==572040== suppressed: 5,120 bytes in 2 blocks ==572040== Rerun with --leak-check=full to see details of leaked memory Curious it only shows 5G total heap usage when I saw it go over 10G in 'top'; which I guess suggests what ever is allocated it's allocated on some humungous structure which is eventually freed. -- You are receiving this mail because: You are the assignee for the bug.
