1.5.1 on windows 7 enterprise: runtime: panic before malloc heap initialized

[Torsten Kleiber]

Hi!

 

I try to use 1.5.1 on a windows box th first time.

Simple starting only "vagrant" gets following error output:

 

vagrant
runtime: panic before malloc heap initialized
fatal error: runtime: cannot reserve arena virtual address space

runtime stack:

 

On another maching with window7 home I had no problems before.

 

Kind regards

Torsten

 

[Mitchell Hashimoto]

Torsten,

This is the first time I've heard of this. Some basic googling appears
to say that this error happens if you don't have enough virtual
memory available. The launcher for Vagrant is now written in Go for
Windows. While it uses an extremely small amount of physical RAM, Go
supposedly requires quite a bit of virtual RAM to start up.

Best,
Mitchell

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

[Torsten Kleiber]

Hi Mitchell,

 

my 64bit Machine has 8 GB physical Memory, from which are 5,5 available, when I call vagrant. Additional there is a swap file of 12 GB.

This seems to be enough to me?

 

Kind regards

Torsten

[Alvaro Miranda Aguilera]

What is the amount of memory allocated to your vm?

--

[Torsten Kleiber]

I don't have actually one vm. I simple call "vagrant", which should show the help screen.

[Torsten Kleiber]

Hi!

 

After dropping an recreating the pagefile several times and different ways (different drives, fixed vs. system managed, sizes) the error goes away.

The only change is to use the recommended size as fixed size instead of using some size above this recommandation.

 

Kind regards 

[Torsten Kleiber]

Hi!

 

After some reboots the error comes up again!

 

Kind regards 

[Quinton McCombs]

I have started running into this problem as well.  Did you ever find a solution?

[Quinton McCombs]

BTW - I am running windows 7 Pro 64 bit.  

To get past this problem I went back to Vagrant 1.4.3.

On Wednesday, April 9, 2014 3:12:46 AM UTC-5, Torsten Kleiber wrote:

[Torsten Kleiber]

Hi!

 

This solves the problem here too, I don't know any other solution at the moment.

I hope that somebody of vagrant pay attention to this, as we can not use new features and fixes of newer versions of this.

Is there a way to open a bug for this?

 

Kind regards

Torsten

[Maximilien Thiel]

Hi,

I had the same problem with Vagrant 1.5.x and the recently released 1.6.
Trying to call vagrant init or simply vagrant from the windows command line failed.
Calling it throught Cygwin did work.

I'm using a Win7 Enterprise 64bit on a 8 core Xeon with 12Go of ram.

Hope this can help some,
MT

[Marc Labbe]

Hi Mitchell,

I am experiencing the same problem. I have a Windows 7 Pro 64bits with 32GB of RAM and I run programs that are significantly more demanding than the simple vagrant command line tool. It is indeed a strange problem considering the fact it works with Cygwin on the same host. It also works on my laptop with way less memory than my workstation.

I am trying to figure out if it could be caused by a conflict with some other tools on my host but so far no luck.

Could it be related to the way the Go program is compiled? I tried to find information about that part but couldn't find anything. What version of the Go compiler is used? Compile + link flags? It there a way for me to compile it myself (is there a repo for it)?

I am willing to try to dig a little more into this.

cheers,

marc

[Alvaro Miranda Aguilera]

On Thu, Jun 19, 2014 at 7:45 AM, Marc Labbe <mrl...@gmail.com> wrote:

Torsten Kleiber

Hello,

I will suggest open a bug for this, however, as there is a known workaround, please specify the same in the bug.

alvaro.