git fetch OOM on Windows

[Steve Kobes]

Recently I'm getting the following running "git fetch origin":

Auto packing the repository in background for optimum performance.

See "git help gc" for manual housekeeping.

fatal: Out of memory, realloc failed

error: failed to run repack

The checkout is on Windows 7 with 64 GB of RAM.  Resource Monitor says git.exe is only using 1.6 GB, so it must be hitting an artificial limit somewhere.

Any suggestions?

Thanks,

Steve

[Trent Apted]

Reducing the number of pack threads may help

My ~/.gitconfig has the following:

  [pack]

      threads = 4

because one day I tried to `git gc --aggressive` on chromium and ran into errors like this.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAjAU%3DYOGj_TJ7%3Dj0KzCJnwvajH-Kf6Y_DSmMtn1Dfrs3F%2BFQQ%40mail.gmail.com.

[Wing-chung Leung]

Just asking for the obvious: are you using 64-bit software (both Windows and Git)? If not 1.6GB is close to the limit.

[Marc-Antoine Ruel]

Robbie, would it be a lot of work to switch to git x64? It could potentially help perf wise too (?)

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAGrfxcLcyhzO%3DB%2BRmjtsyT-1A73TTz1bRUqoNsc2nBicfNOMg%40mail.gmail.com.

[Steve Kobes]

Indeed, git from depot_tools appears to be 32-bit.  Using pack.threads=4 didn't help, but installing 64-bit git from https://git-scm.com/ did.  (I picked the "use with cmd.exe" option during installation, and I had to edit system path to put "C:\Program Files\Git\cmd" ahead of "C:\chrome\depot_tools".)

Filed crbug.com/773101 to fix depot_tools.