[SERVER-6713] 32-bit Windows builds should set the linker option /LARGEADDRESSAWARE Created: 05/Aug/12 Updated: 11/Jul/16 Resolved: 05/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | Windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 32-bit |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
Instead of the standard 2 GB of user address space given to 32-bit processes on Windows, programs built with the /LARGEADDRESSAWARE linker switch are given a 4 GB user address space when running under a 64-bit OS. Comparing builds without and with /LARGEADDRESSAWARE, VMMap shows that we go from a total of 1950 MB of free address space to 3978 MB free. The addition is a block of just under 2 GB starting at address 0x7FFF0000. |
| Comments |
| Comment by auto [ 05/Aug/12 ] |
|
Author: {u'date': u'2012-08-04T17:17:11-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Add /LARGEADDRESSAWARE linker switch to Windows builds to |