all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory #45759

nerotiger · 2021-04-25T16:00:30Z

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

$ go version
1.16.3

Does this issue reproduce with the latest release?

YES

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

go env Output

$ go env
GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="freebsd"
GOOS="freebsd"
GOPATH="/home/water/my_go"
GORACE=""
GOROOT="/home/water/src/go14"
GOTOOLDIR="/home/water/src/go14/pkg/tool/freebsd_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0"
CXX="clang++"
CGO_ENABLED="0"

What did you do?

RUN ./src/all.bash to build the latest version of GO

[water@eid01dev ~/src/go_1g3/src]$ ./all.bash
Building Go cmd/dist using /home/water/src/go14. (go1.4-bootstrap-20170531 freebsd/amd64)
Building Go toolchain1 using /home/water/src/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
./make.bash: line 215: 969 Killed ./cmd/dist/dist bootstrap $buildall $vflag $GO_DISTFLAGS "$@"

What did you expect to see?

Successfully build the latest version of GO.

What did you see instead?

Process killed with SWAP of 2GB.

[water@eid01dev ~/src/go_1g3/src]$ dmesg
pid 1434 (compile), jid 0, uid 500, was killed: out of swap space
pid 969 (dist), jid 0, uid 500, was killed: out of swap space
pid 1270 (go_bootstrap), jid 0, uid 500, was killed: out of swap space

[water@eid01dev ~/src/go_1g3/src]$ top
last pid: 1465; load averages: 0.56, 0.64, 0.39 up 0+00:10:08 15:53:03
21 processes: 1 running, 20 sleeping
CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 14M Active, 14M Inact, 68K Laundry, 92M Wired, 54M Buf, 339M Free
Swap: 2048M Total, 12M Used, 2036M Free

[water@eid01dev ~/src/go_1g3/src]$ swapctl -l
Device: 1024-blocks Used:
/dev/md99 2097152 12012

The text was updated successfully, but these errors were encountered:

nerotiger · 2021-04-25T16:10:05Z

go build cmd/compile/internal/ssa: /home/water/src/go_1g3/pkg/tool/freebsd_amd64/compile: signal: killed

same with go1.14.2 freebsd/amd64 bootstrap.

cherrymui · 2021-04-26T16:45:42Z

How many CPU cores do you have on your machine? Maybe set GOMAXPROCS=1 to limit the parallelism?

339M Free

This is really too small to build Go toolchain. It might work with sufficient swap space, but it will put a lot of pressure on swap and probably very slow.

nerotiger · 2021-04-26T18:47:37Z

How many CPU cores do you have on your machine? Maybe set GOMAXPROCS=1 to limit the parallelism?

XEN: Hypervisor version 4.2 detected.
CPU: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz (2400.04-MHz K8-class CPU)

1 core, in this case. but I don't think 2 cores will help. I will try for non-paralyzed tonight.

339M Free

Hypervisor: Origin = "XenVMMXenVMM"
real memory  = 536870912 (512 MB)
avail memory = 478728192 (456 MB)

This is really too small to build Go toolchain. It might work with sufficient swap space, but it will put a lot of pressure on swap and probably very slow.

I have freed up to 2GB of swap, however the process was killed.
So what is the official minimum memory requirement for GO to compile?
This amazon cloud service served apache2.2 and mysql8 quite smoothly.
And it can run go1.14.2 (built binary) without any problem.

cherrymui · 2021-04-26T18:59:02Z

So what is the official minimum memory requirement for GO to compile?

I vaguely remember it was mentioned somewhere but I couldn't find it. Maybe @ianlancetaylor @davecheney could provide a better answer.

And it can run go1.14.2 (built binary) without any problem.

Yes, running compiled Go programs are okay. It just needs more memory to build the toolchain itself (make.bash or all.bash).

nerotiger · 2021-04-26T19:16:22Z

So what is the official minimum memory requirement for GO to compile?

I vaguely remember it was mentioned somewhere but I couldn't find it. Maybe @ianlancetaylor @davecheney could provide a better answer.

And it can run go1.14.2 (built binary) without any problem.

Yes, running compiled Go programs are okay. It just needs more memory to build the toolchain itself (make.bash or all.bash).

I never realized a programming language, is so picky and required those many resources.
I'll have to just stick to 1.4 c-complied version for basic features then.

cherrymui · 2021-04-26T19:20:49Z

I never realized a programming language, is so picky and required those many resources.

Have you tried to compile a C toolchain from source, like GCC or LLVM on that machine ?

nerotiger · 2021-04-27T01:12:28Z

Have you tried to compile a C toolchain from source, like GCC or LLVM on that machine ?

Yes, go1.4 (bootstrap) worked just fine. // go1.4-bootstrap-20171003.tar.gz

networkimprov · 2021-05-16T05:00:00Z

I recall seeing a problem with Go on FreeBSD 12.1 that was fixed by upgrading to 12.2. I don't have a reference.

nerotiger · 2021-05-16T05:25:10Z

I will try on 12.2 later, however, Linux CentOS 7 may also fail due to the shortage of memory.

…

On Sun, 16 May 2021 at 07:00, Liam ***@***.***> wrote: I recall seeing a problem with Go on FreeBSD 12.1 that was fixed by upgrading to 12.2. I don't have a reference. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#45759 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6N3UK6R2DTYCPUVGOM4XDTN5GN7ANCNFSM43RNJPPQ> .

-- This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ********************************************************************** Ce message electronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci apres "le message" ), sont confidentiels et destines exclusivement a l'usage de la personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites. **********************************************************************

seankhliao · 2022-06-12T00:45:45Z

Closing as not a bug

cherrymui added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Apr 26, 2021

seankhliao changed the title ~~freebsd12.1 - go1.16.3 - build failed - out of memory~~ all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory Jun 18, 2021

seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2022

golang locked and limited conversation to collaborators Jun 12, 2023

gopherbot added the FrozenDueToAge label Jun 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory #45759

all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory #45759

nerotiger commented Apr 25, 2021 •

edited

nerotiger commented Apr 25, 2021 •

edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 26, 2021 •

edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 26, 2021 •

edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 27, 2021

networkimprov commented May 16, 2021

nerotiger commented May 16, 2021 via email

seankhliao commented Jun 12, 2022

all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory #45759

all.bash: freebsd12.1 - go1.16.3 - build failed - out of memory #45759

Comments

nerotiger commented Apr 25, 2021 • edited

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

Does this issue reproduce with the latest release?

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

What did you do?

What did you expect to see?

What did you see instead?

nerotiger commented Apr 25, 2021 • edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 26, 2021 • edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 26, 2021 • edited

cherrymui commented Apr 26, 2021

nerotiger commented Apr 27, 2021

networkimprov commented May 16, 2021

nerotiger commented May 16, 2021 via email

seankhliao commented Jun 12, 2022

nerotiger commented Apr 25, 2021 •

edited

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

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

nerotiger commented Apr 25, 2021 •

edited

nerotiger commented Apr 26, 2021 •

edited

nerotiger commented Apr 26, 2021 •

edited