Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows snapshot build v11 runs high on memory, sometimes out of memory #45095

Open
llvmbot opened this issue Apr 30, 2020 · 0 comments
Open
Labels
bugzilla Issues migrated from bugzilla c++ clang:to-be-triaged Should not be used for new issues platform:windows

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Apr 30, 2020

Bugzilla Link 45750
Version trunk
OS Windows NT
Reporter LLVM Bugzilla Contributor
CC @DougGregor,@zygoloid

Extended Description

First, please note this was only a problem seen with the Windows snapshot build v11 from:

https://llvm.org/builds/
LLVM-11.0.0-2663a25f-win64.exe

This is not a problem with v10 nor v9 from:

https://releases.llvm.org/download.html
LLVM-10.0.0-win64.exe
LLVM-9.0.0-win64.exe

I see that v10 (20 Mar 2020) is newer than v11 (3 February 2020), so the v11 page or build is outdated?
https://releases.llvm.org/

The problem I had, when building with clang from Visual Studio 2019, is it used a lot of memory (20gb+), sometimes ending with the LLVM out of memory error.

With v10 and v9, it runs below 1gb.

I can provide more details. But first worth considering the Windows snapshot page is replaced by the releases page?

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@Endilll Endilll added platform:windows clang:to-be-triaged Should not be used for new issues labels Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla c++ clang:to-be-triaged Should not be used for new issues platform:windows
Projects
None yet
Development

No branches or pull requests

2 participants