FAQ
I have compiled in VirtualBox a program having 50,000 lines of code.

When the memory available to VirtualBox is 1.8 Gb, 6g stops with the
message "out of memory".
I increased the memory avalable to VirtualBox to 2.4 Gb and it compiles
with no problem.

Using "top", I could see that 6g is using more than 1.5 Gb of memory during
compilation.

Is it expected that the compiler uses this amount of memory, or have I come
across some pathological case ?

uname -a
   Linux nico-Qiana-Xfce 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

   go version go1.3.2 linux/amd64

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Jonas August at Jul 6, 2015 at 12:39 am
    Try Go 1.4.2 from https://golang.org/dl/.
    On Sunday, July 5, 2015 at 8:31:44 PM UTC-4, nicolas riesch wrote:

    I have compiled in VirtualBox a program having 50,000 lines of code.

    When the memory available to VirtualBox is 1.8 Gb, 6g stops with the
    message "out of memory".
    I increased the memory avalable to VirtualBox to 2.4 Gb and it compiles
    with no problem.

    Using "top", I could see that 6g is using more than 1.5 Gb of memory
    during compilation.

    Is it expected that the compiler uses this amount of memory, or have I
    come across some pathological case ?

    uname -a
    Linux nico-Qiana-Xfce 3.13.0-24-generic #47-Ubuntu SMP Fri May 2
    23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    go version go1.3.2 linux/amd64
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Nicolas riesch at Jul 6, 2015 at 9:07 am
    With Go 1.4.2, it is worse, I cannot compile.

    nico@nico-Qiana-Xfce ~/z_go/src/rsql/data $ go test
       go build rsql/data: /usr/local/go/pkg/tool/linux_amd64/6g: signal: killed
       FAIL rsql/data [build failed]


    Before the compilation fails, "top" shows:

    Tasks: 147 total, 2 running, 145 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 91.1 us, 8.6 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.3 hi, 0.0 si,
      0.0 st
    KiB Mem: 2339900 total, 1980540 used, 359360 free, 6100 buffers
    KiB Swap: 0 total, 0 used, 0 free. 105128 cached Mem

         PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
    COMMAND
                    3467 nico 20 0 1518364 1.446g 788 R 98.7 64.8
    0:40.89 6g
                              1548 root 20 0 370416 78924 15688 S 0.7
      3.4 1:03.82 Xorg
                                  3403 nico 20 0 25228 1620 1116 R
      0.3 0.1 0:00.23 top
                                      3438 root 20 0 0 0
      0 S 0.3 0.0 0:00.02 kworker/u2:2
                                               1 root 20 0 34032 1920
          4 S 0.0 0.1 0:03.50 init
                                                     2 root 20 0 0
          0 0 S 0.0 0.0 0:00.00 kthreadd

    go version go1.4.2 linux/amd64


    Le lundi 6 juillet 2015 02:31:44 UTC+2, nicolas riesch a écrit :
    I have compiled in VirtualBox a program having 50,000 lines of code.

    When the memory available to VirtualBox is 1.8 Gb, 6g stops with the
    message "out of memory".
    I increased the memory avalable to VirtualBox to 2.4 Gb and it compiles
    with no problem.

    Using "top", I could see that 6g is using more than 1.5 Gb of memory
    during compilation.

    Is it expected that the compiler uses this amount of memory, or have I
    come across some pathological case ?

    uname -a
    Linux nico-Qiana-Xfce 3.13.0-24-generic #47-Ubuntu SMP Fri May 2
    23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    go version go1.3.2 linux/amd64
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Nicolas riesch at Jul 6, 2015 at 9:13 am
    Sorry, some bad formatting in last message:

        PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
       3467 nico 20 0 1518364 1.446g 788 R 98.7 64.8 0:40.89 6g
       1548 root 20 0 370416 78924 15688 S 0.7 3.4 1:03.82 Xorg


    Le lundi 6 juillet 2015 02:31:44 UTC+2, nicolas riesch a écrit :
    I have compiled in VirtualBox a program having 50,000 lines of code.

    When the memory available to VirtualBox is 1.8 Gb, 6g stops with the
    message "out of memory".
    I increased the memory avalable to VirtualBox to 2.4 Gb and it compiles
    with no problem.

    Using "top", I could see that 6g is using more than 1.5 Gb of memory
    during compilation.

    Is it expected that the compiler uses this amount of memory, or have I
    come across some pathological case ?

    uname -a
    Linux nico-Qiana-Xfce 3.13.0-24-generic #47-Ubuntu SMP Fri May 2
    23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    go version go1.3.2 linux/amd64
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Geert-Johan Riemer at Jul 6, 2015 at 1:29 pm
    What is in the 50k lines of code? Did you maybe embed large resources
    (files, images, etc) as string or byte slice?
    On Monday, 6 July 2015 11:13:03 UTC+2, nicolas riesch wrote:

    Sorry, some bad formatting in last message:

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    3467 nico 20 0 1518364 1.446g 788 R 98.7 64.8 0:40.89 6g
    1548 root 20 0 370416 78924 15688 S 0.7 3.4 1:03.82 Xorg


    Le lundi 6 juillet 2015 02:31:44 UTC+2, nicolas riesch a écrit :
    I have compiled in VirtualBox a program having 50,000 lines of code.

    When the memory available to VirtualBox is 1.8 Gb, 6g stops with the
    message "out of memory".
    I increased the memory avalable to VirtualBox to 2.4 Gb and it compiles
    with no problem.

    Using "top", I could see that 6g is using more than 1.5 Gb of memory
    during compilation.

    Is it expected that the compiler uses this amount of memory, or have I
    come across some pathological case ?

    uname -a
    Linux nico-Qiana-Xfce 3.13.0-24-generic #47-Ubuntu SMP Fri May 2
    23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    go version go1.3.2 linux/amd64
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Nicolas riesch at Jul 6, 2015 at 8:03 pm
    Issue has been opened:

    https://github.com/golang/go/issues/11612



    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJul 6, '15 at 12:31a
activeJul 6, '15 at 8:03p
posts6
users3
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase