| Summary: | webkit-gtk build failed randomly with "Memory exhausted" | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Kai Kang <kai.kang> |
| Component: | devtools / tool chain | Assignee: | Joe Slater <joe.slater> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | kai.kang, meta.mr.watcher, meta.watcher, ross.burton, sgw |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Kai Kang
2013-09-10 10:16:18 UTC
LDFLAGS += " -Wl,--no-keep-memory" is apparently the idiomatic way of resolving this. It does impact performance so we should benchmark a build and see it that's a real or theoretical impact. If its hypothetical then we can just add it, otherwise how about adding it to the recipe as a comment. Kai, are your hosts running a 32 or 64 bit distro? After check the log, it fails on both 32 and 64 bits hosts. Most( about 90%) failures are on i686 machines. Working theory is that on a 32-bit host you're doomed because you can only allocate 3G per process, and the webkit library is larger than that during link. On a 64-bit host you'll just be restricted by RAM+swap limits. |