Summary: | USE="tcmalloc" means different thing in chromium | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hanno Böck <hanno> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hanno Böck
2014-01-15 17:22:38 UTC
The tcmalloc use flag does NOT toggle between bundled tcmalloc and system tcmalloc. Rather, it toggles between building against tcmalloc (which happens to be bundled), or traditional malloc (provided by glibc). oh sorry, seems I misread it. Then it makes more sense. We may close this bug, but obviously this opens the question why it isn't using the system wide one. (but I know chromium+bundling is a complicated topic) (In reply to Hanno Boeck from comment #2) > (but I know chromium+bundling is a complicated topic) I think it's solved for most libs that are actually packaged and designed to be used as shared libraries. For the tcmalloc, please see https://codereview.chromium.org/12224030 which contains several comments from other Chromium developers. |