| Summary: | sys-apps/sandbox: www-client/chromium[component-build,tcmalloc] hangs while building v8_context_snapshot_generator | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Stephan Hartmann (RETIRED) <sultan> |
| Component: | Sandbox | Assignee: | Sandbox Maintainers <sandbox> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | chromium, sam, slyfox |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | gdb backtrace | ||
|
Description
Stephan Hartmann (RETIRED)
2019-10-01 13:04:24 UTC
Nice backtrace! It shows that tcmalloc hooked mmap() and broke sb_mmap() by recursing in constructors. Let's see if we can extend override blacklist with this new symbol. We have dropped USE=tcmalloc from chromium ebuilds. Build system switches off any special allocator with component builds automatically. (In reply to Stephan Hartmann from comment #2) > We have dropped USE=tcmalloc from chromium ebuilds. Build system switches > off any special allocator with component builds automatically. The current default allocator on linux is partition allocator, should we pass `use_allocator="none"` to use the libc allocator? https://github.com/chromium/chromium/blob/master/base/allocator/allocator.gni |