Linker running out of heap memory

General JUCE discussion
1

I started getting build fail due to linker running out of heap space.
I am on visual studio 2019 , win10 x64 32gb ram.
I was able to fix that issue by changing “Preferred Build Tool Architecture” from “default” to “64-bit (x64)” in the project configuration properties.
The issue now is that everytime i restart the project the setting gets overwritten by the projucer…
How can i make that setting stick?

2

Looks like there could be a compiler flag that makes Visual Studio output the full paths to the compiler tools it is using. This would confirm whether or not the 64-bit linker is being used.

Check out the “Choice of toolset is important” section of this page.

This could be added to the “Extra Compiler Flags” section of the jucer project.

3

Set the environment variable PreferredToolArchitecture to x64

2 Likes
4

@RolandMR is right. The compiler option just makes Visual Studio output the paths to the compiler tools so that you can check that the correct ones are being used.

5

Setting the environment variable seems to work.
thanks.

6

Hello, we have similar issues, where is this variable please? :wink:

7

Windows Key + Break

From there, select “Advanced system settings” → “Environment Variables”.

1 Like
8

Awesome, thanks :wink:

9

I’m running into this same issue. Can someone explain how to correct this in Projucer (not the VS project)?

I tried setting the environment variable with no success.

10

Have you tried using the Extra Compiler flag: /bigobj

Rail

11

**/bigobj** increases the number of sections that an object file can contain.

Not quite the same thing as specifying the preferred toolset…?

12

set PreferredToolArchitecture=x64 looks promising. Perhaps you can put that in the pre-build command section?

13

I tried a bunch of combinations and ended up with:

in Extra Compiler Flags, I added:
/bigobj

in Pre-Build Command, I added:
set PreferredToolArchitecture=x64

And also set BinaryData.cpp size limit to:
20mb

THEN it finally compiled & linked in VS2019. None of those were needed in VS2017.

After quite a bit of googling, it looks like Microsoft supposedly fixed several bugs about default toolset, compiler and/or linker running out of memory, but I have the latest version and still hit those errors.

I guess I’ll just go back to VS2017. Life was easier.

1 Like
14

I’m having this issue today with VS 2019. I’m a Mac guy, and I’m running Windows 10 on a Windows box via Remote desktop with a Mac Keyboard. So what does this mean exactly? How/where do I set an Environment Variable on Windows, i.e. “Set the environment variable PreferredToolArchitecture to x64” ?

Is this something I can set in the Projucer?

I tried in VS2019 Exporter, for Debug and Release, in the Pre-Build Command:
set PreferredToolArchitecture=x64

… but I can still see it is using the 32-bit tools from the Task Manager.

Thanks.