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

cmd/compile: "too many open files in system" on macos Ventura #54833

Open
jamesli2021 opened this issue Sep 2, 2022 · 2 comments
Open

cmd/compile: "too many open files in system" on macos Ventura #54833

jamesli2021 opened this issue Sep 2, 2022 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@jamesli2021
Copy link

jamesli2021 commented Sep 2, 2022

I'm running macOS Ventura and update to the latest beta build to test with Go 1.19. There could be a bug in Go reading files which might be affected when macOS Ventura is release to the public. Go 1.18.5 is working fine.

What version of Go are you using (go version)?

go version go1.19 darwin/arm64

Does this issue reproduce with the latest release?

Yes, 1.19

What operating system and processor architecture are you using (go env)?

macOS Ventura, M1 (arm)

What did you do?

Compiling a simple Go project and I get "too many open files in system".

What did you expect to see?

Able to compile as Go 1.18.5 which is working fine without error.

What did you see instead?

"... too many open files in system" appear in the terminal when ran "go build ." command.

@heschi heschi changed the title affected/package: Go 1.19 on macos Ventura cmd/compile: "too many open files in system" on macos Ventura Sep 2, 2022
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Sep 2, 2022
@heschi heschi added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Sep 2, 2022
@heschi heschi added this to the Go1.20 milestone Sep 2, 2022
@heschi heschi added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 2, 2022
@heschi
Copy link
Contributor

heschi commented Sep 2, 2022

cc @golang/compiler

Please provide a full reproducer, log, and the output of go env.

@jamesli2021
Copy link
Author

jamesli2021 commented Sep 3, 2022

Here go env output:

go env                   
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/s/Library/Caches/go-build"
GOENV="/Users/s/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/s/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/s/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/s/Documents/aaa/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/q6/vgzzlsv56j5_jk6_ysj8ld0c0000gn/T/go-build4248313789=/tmp/go-build -gno-record-gcc-switches -fno-common"

@seankhliao seankhliao added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Status: No status
Development

No branches or pull requests

4 participants