ungoogled-chromium: Large memory leak in main process over several days
There seems to be a memory leak in the Debian 9 amd64 binaries I’ve built.
Current reports: On my machine, I have seen the memory footprint of the main process grow from about 170 MB to over 400 MB in the span of 3 days (with my binaries here). @ik9999 has reported growth of over 2 GB on the main process within 3-5 days for my 64.0.3282.186-1 Debian 9 amd64 binaries on Debian testing (buster).
Some potential avenues to investigate:
- Sift through the patches to see if anything there could be causing any problems.
- See if any of ungoogled-chromium’s deriving projects, such as Inox or Debian’s Chromium, have memory leaks. This can narrow down the potentially problematic patches.
- See if
linux_portable(as of version 65) is affected by memory leaks to this degree. - Use LeakSanitizer based on
linux_portable(as of version 65).
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 22 (9 by maintainers)
If memory usage is not concerning so far, then I’ll close this issue. Until (or unless) ungoogled-chromium formalizes development with better practices (i.e. running code testing and analysis tools that Google uses over the code), I don’t see any point in digging deeper into memory usage; any attempt to do so could end up futile with updates and new features.