Bug report: Corrupt pack file after committing a large file (>4 GB?)

Dear maintainer,

There is a bug where committing a large file corrupts the pack file in
Windows. Steps to recreate are:

1. git init
2. stage and commit a file larger than 4 GB (not entirely sure about this size)
3. git checkout -f

The file checked out is much smaller than the original file size.

This behavior is surprising. If git does not support large files, I
would at least expect an error message when staging or committing. I
have post a question on StackOverflow regrading this issue, and has
been confirmed by another user. (question id: 44022897)

Best regards,

David Chen