Timeline for G_realloc: unable to allocate 46320000 bytes of memory while managing large .xyz through v.in.ascii
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:34 | history | edited | CommunityBot |
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
|
|
| Jan 29, 2017 at 19:12 | history | edited | PolyGeo♦ | CC BY-SA 3.0 |
deleted 25 characters in body
|
| Mar 16, 2015 at 8:01 | history | edited | Pavel V. | CC BY-SA 3.0 |
added 57 characters in body
|
| Mar 15, 2015 at 16:50 | answer | added | markusN | timeline score: 2 | |
| Mar 13, 2015 at 12:48 | comment | added | Vince | Obviously 4Gb is too small for swap. I never hit virtual RAM if I can avoid it, but my W7 systems have 8Gb RAM (which feels too small, so I'm leaning towards an upgrade to 16Gb soon). 3-D GIS requires significant RAM, and swap is five orders of magnitude slower than physical memory (6ms vs 40ns seek). Try increasing swap, then report what Windows has to say about available memory. | |
| Mar 13, 2015 at 11:36 | history | edited | Pavel V. | CC BY-SA 3.0 |
added 85 characters in body
|
| Mar 13, 2015 at 11:08 | comment | added | Vince | 45Mb might be small, but it's unlikely you have the full 2Gb available -- Windows 7 steals more that half of that without any other resident applications. Other variables include swap space ("virtual memory") and the application word size (32-bit applications can't address more than 1-1.2 Gb total memory, ever), and the amount of RAM dedicated to other things. Please edit the question to include the OS, swap, word size, and an indication of what the OS reports as free as the job runs. | |
| Mar 13, 2015 at 7:39 | history | asked | Pavel V. | CC BY-SA 3.0 |