Build error LNK1210 "Exceeded internal ILK size limit"

[harry]

Hi,

I've seen this error pop up every now and again, but I can't see any
true solution. I'm building on a 64-bit machine with VS2008 SP1. I
have 6 GB RAM and an SSD with no additional virtual memory.

I have set the startup project to the 'chrome' project only, and I
have tried setting incremental linking on and off.

After each build I tried deleting everything in the Debug/ folder, as
well as cleaning the project (just incase - although the wiki page
this doesn't really do much).

Any ideas?

[Ryosuke Niwa]

The last time I checked, 6GB of physical RAM wasn't enough to build Chromium without swapping.

- Ryosuke

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-dev

[harry]

I see. What is the recommended minimum?

On Feb 7, 6:42 pm, Ryosuke Niwa <rn...@google.com> wrote:
> The last time I checked, 6GB of physical RAM wasn't enough to build
> Chromium without swapping.
>
> - Ryosuke
>
>
>
>
>
>
>
> On Tue, Feb 7, 2012 at 10:26 AM, harry <arr...@gmail.com> wrote:
> > Hi,
>
> > I've seen this error pop up every now and again, but I can't see any
> > true solution. I'm building on a 64-bit machine with VS2008 SP1. I
> > have 6 GB RAM and an SSD with no additional virtual memory.
>
> > I have set the startup project to the 'chrome' project only, and I
> > have tried setting incremental linking on and off.
>
> > After each build I tried deleting everything in the Debug/ folder, as
> > well as cleaning the project (just incase - although the wiki page
> > this doesn't really do much).
>
> > Any ideas?
>
> > --

> > Chromium Developers mailing list: chromium-...@chromium.org

[Marc-Antoine Ruel]

First, do not disable virtual memory. So at least you'll be able to build at all. Do that before anything else.

Then if you still find it I/O bound, you can use readyboost, it does help with low memory situation like yours. Probably the effect will be minimal with a SSD.

Most, if not all, devs have 12gb of ram or more.

M-A

Chromium Developers mailing list: chromi...@chromium.org

[Dominic Mazzoni]

You should be able to do a Release build. That will require less RAM and depending on what you need to do, that might be okay.

This should also help:

http://www.chromium.org/developers/how-tos/component-build

- Dominic

Chromium Developers mailing list: chromi...@chromium.org

[Scott Byer]

<rant>

Where did this myth of disabling Windows' virtual memory 'making things better' come from? It's just awful advice - never disable the paging file! It doesn't improve performance. And these days, I don't even do the old trick of wiring min == max, Windows does fine at managing the paging file on it's own, and at keeping RAM reasonably optimally occupied (unused RAM is wasted RAM).

If I had a nickel for every 'Photoshop makes my machine crash' bug which traced back to someone pulling that goofy no-page-file stunt...

</rant>

Sigh

[harry]

Sorry, I was wrong when I said I had no paging file. I do, it's just
managed by the system. I set up another paging file with a set amount
of 5000-20000 on a different drive. I am still getting this exceeded
ILK size limit error though. I haven't cleaned/deleted Debug folder
since the last build - is this a necessary step?

[Aaron Leventhal]

I had these errors until I enabled the component build. I'm not using the incremental linker right now, though, as I suspect that caused me issues before.

Aaron

[Scott Byer]

Yeah, the incremental linker takes more address space to do it's thing, and in a non-component build may actually be exhausting the space it has to work with (if it's not marked as large address aware, it only gets 2GB of address space). Go with the component build. VS2010 linker seems to be better about this (dumpbin /HEADERS on VS2010's link.exe shows 'large address aware' set, so it's got 3GB of address space).

[harry]

I appreciate the help everyone. I ended up building in Release (which
works) as this is fine for my needs right now.

> >> Chromium Developers mailing list: chromium-...@chromium.org

> >> View archives, change email options, or unsubscribe:
> >>    http://groups.google.com/a/chromium.org/group/chromium-dev
>
> >  --

> > Chromium Developers mailing list: chromium-...@chromium.org

[harry]

I appreciate the help everyone. I ended up building in Release (which
works) as this is fine for my needs right now.

> >> Chromium Developers mailing list: chromium-...@chromium.org

> >> View archives, change email options, or unsubscribe:
> >>    http://groups.google.com/a/chromium.org/group/chromium-dev
>
> >  --

> > Chromium Developers mailing list: chromium-...@chromium.org

[John Alway]

Hello!  :-)

I'm getting the same problem!

I have VS2010, Windows 7, 64 bit OS, and have 8 GB of ram.

I get the error:

3>LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO

in the Chrome project.

They claim the limit is hard coded into VS2010.    If this is the case, then I'd imagine no one was able to build in VS2010 without turning off Incremental linking?

Thanks!

...John

[John Alway]

Release mode did compile.   Still working on debug mode.

[Daniel Bratell]

Den 2013-05-26 02:36:21 skrev John Alway <alwaysl...@gmail.com>:

> Hello! :-)
>
> I'm getting the same problem!
>
> I have VS2010, Windows 7, 64 bit OS, and have 8 GB of ram.
>
> I get the error:
> 3>LINK : fatal error LNK1210: exceeded internal ILK size limit; link with
> /INCREMENTAL:NO
> in the Chrome project.

You can, for development, get around this by building a "component build"
(many dlls instead of one big exe). See
http://www.chromium.org/developers/how-tos/component-build

/Daniel

[Jack]

I'll add a little something here.

It's not that you can, it's that since v25 IIRC the static build cannot be done anymore 

in debug mode. The pdb file became too big for VS to generate it. 

 

--
--
Chromium Developers mailing list: chromi...@chromium.org

View archives, change email options, or unsubscribe:   http://groups.google.com/a/chromium.org/group/chromium-dev

--
Seriously, Jack

[Abhijeet Kandalkar]

Hello All,

same problem!

VS2010, 

Windows 7, 64 bit OS, 

and have 10 GB of ram.

Any help !! Did any one figure out the solution

[Daniel Bratell]

On Sun, 24 Nov 2013 16:44:06 +0100, Abhijeet Kandalkar <kandalkar....@gmail.com> wrote:

Hello All,

same problem!

VS2010, 

Windows 7, 64 bit OS, 

and have 10 GB of ram.

Any help !! Did any one figure out the solution

It is in the mails you quoted. Not a good "solution" but a workaround that allows people to get some work done (component builds instead of static builds).

I believe Google also has split chrome.exe into two different binaries but I am not sure how that applies to Chromuim and content_shell.

/Daniel

[Zachary Turner]

scottmg has been doing some work to get chrome compiling on VS2013.  When it's complete, they have a 64/32-bit cross toolchain, so in theory any memory related problems should disappear.  Not sure how close it is to being ready-for-primetime though.

[Scott Graham]

I've switched to 2013 locally. If you'd like to test to see if it helps, you can "set GYP_MSVS_VERSION=2013" before gclient runhooks. If you have 2013 Pro, gyp will prefer the x64-x86 cross compiler. There's no cross compiler available in Express.

This will probably break occasionally, as it's not on the main waterfall yet.