"no space on device" in thinlto and cfi builds on Windows |
|||
Issue descriptionExample build exhibiting the problem: https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.clang%2FToTWinCFI64%2F1525%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout This bug is to investigate if this is simply because these configurations need more space, or because they are using more space than they should.
,
Aug 17
We are leaking tempfiles. This can be reproduced by doing a CFI build (ninja all) and stopping it with control+C during linking. I also wrote a small reproducer that spawns 100 threads, each of which creates a TempFile and then tries to keep() it to the same final name as every other thread, and the main thread exits before all threads have finished.
,
Aug 22
,
Aug 23
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6b340a5eff263abad65cecb22ce840baf34be2be commit 6b340a5eff263abad65cecb22ce840baf34be2be Author: inglorion <inglorion@chromium.org> Date: Thu Aug 23 03:04:45 2018 Stop using the ThinLTO cache with lld-link lld-link can use a cache to speed up ThinLTO builds. Unfortunately, this cache leaks temporary files on Windows, causing storage to fill up. Until this has been addressed, this disables the cache, avoiding the problem. Bug: 871962 Change-Id: I415162233bc8855b3d7e237e80c23cbbc24bcfeb Reviewed-on: https://chromium-review.googlesource.com/1185856 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Bob Haarman <inglorion@chromium.org> Cr-Commit-Position: refs/heads/master@{#585380} [modify] https://crrev.com/6b340a5eff263abad65cecb22ce840baf34be2be/build/config/compiler/BUILD.gn
,
Aug 27
We are no longer running out of disk space, so I'm closing this bug. For the longer term, we are re-architecting the way we do ThinLTO builds. crbug.com/877722 tracks that effort. |
|||
►
Sign in to add a comment |
|||
Comment 1 by inglorion@chromium.org
, Aug 7