Hi I've built TestGtkEmbed from current mozilla-central trunk. Starting TestGtkEmbed through valgrind (with about:open) and then closing it via the File menu, valgrind is complaining about a lot of leaks.
==20759== HEAP SUMMARY: ==20759== in use at exit: 834,159 bytes in 8,450 blocks ==20759== total heap usage: 55,254 allocs, 46,804 frees, 12,056,530 bytes allocated ==20759== ==20759== LEAK SUMMARY: ==20759== definitely lost: 2,080 bytes in 8 blocks ==20759== indirectly lost: 7,720 bytes in 382 blocks ==20759== possibly lost: 400,058 bytes in 2,762 blocks ==20759== still reachable: 424,301 bytes in 5,298 blocks ==20759== suppressed: 0 bytes in 0 blocks ==20759== Rerun with --leak-check=full to see details of leaked memory ==20759== Most of the "possible" leaks seem to stem from various libraries, but others from TestGtkEmbed.cpp. I'm just curious, is there something wrong with my build or do you also see these leaks? Is TestGtkEmbed.cpp the best basis for embedding mozilla into a gtk app? Thanks, Stefan _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
