New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 793096 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Tons of tmp files are generated in "Link Chrome" Step when building Chrome for caroline

Project Member Reported by x...@chromium.org, Dec 7 2017

Issue description

From yesterday (12/06), when building Chrome for caroline board, tons of tmp files are generated in /tmp directory and consume more than 10gb space of the root partition of the file system. Eventually there is no space left on the root partition, and I got error like:

ninja: Entering directory `out_caroline/Release'
[40281/40281] LINK ./chrome
FAILED: chrome 
python "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- x86_64-cros-linux-gnu-clang++ -B/work/chromiumos/.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+target_toolchain/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.27.0-gold -Wno-unknown-warning-option -pie -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=gold -B../../third_party/binutils/Linux_x64/Release/bin -Wl,--threads -Wl,--thread-count=4 -Wl,--icf=all -flto=thin -Wl,-plugin-opt,jobs=8 -fwhole-program-vtables -m64 -Wl,-O1 -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib64 -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib64 -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib64 -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib64 -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib64 -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib64 -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -L../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=. -Wl,--disable-new-dtags -L/work/chromiumos/.cros_cache/chrome-sdk/tarballs/caroline+10193.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib64 -Wl,-O1 -Wl,-O2 -Wl,--as-needed -Wl,-plugin-opt,-import-instr-limit=30 -stdlib=libc++ -o "./chrome" -Wl,--start-group @"./chrome.rsp"  -Wl,--end-group   -ldl -lpthread -lrt -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -ldbus-1 -lcups -lz -lm -lcrypt -lfontconfig -lexpat -lresolv -lfreetype -lasound -lcras -ldrm -lharfbuzz -lxkbcommon -lgestures -levdev -lgbm -lpci -lEGL -lGLESv2 -lsync -lffi 
LLVM ERROR: IO failure on output stream.
LLVM ERROR: IO failure on output stream.
LLVM ERROR: IO failure on output stream.
clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

The error is only seen on caroline and not on other boards. Anyone has a clue?
 

Comment 1 by warx@chromium.org, Dec 7 2017

FWIW, the >10g files generated are lto-llvm*.o

Comment 2 by r...@chromium.org, Dec 8 2017

Components: Infra>Client>Chrome
Owner: yunlian@chromium.org
Status: Assigned (was: Untriaged)
This seems related to  bug 707803 , so assigning to owner of that.
The CL was landed, but we need to wait for Chrome uprev to make it work.
Status: Verified (was: Assigned)

Sign in to add a comment