Opened 4 years ago

Closed 3 years ago

#2758 closed defect (invalid)

i.gensigset error G_calloc: unable to allocate 115671215 * 8 bytes of memory at lib/imagery/sigset.c:24

Reported by: shobhitpipil Owned by: grass-dev@…
Priority: critical Milestone: 7.2.0
Component: Raster Version: 7.0.1
Keywords: Cc:
CPU: x86-64 Platform: MSWindows 8

Description

G_calloc: unable to allocate 115671215 * 8 bytes of memory at lib/imagery/sigset.c:24

Attachments (1)

Picture1.png (107.2 KB) - added by shobhitpipil 4 years ago.

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by shobhitpipil

Attachment: Picture1.png added

comment:1 Changed 4 years ago by shobhitpipil

g.region -p                                                                     
projection: 1 (UTM)
zone:       44
datum:      wgs84
ellipsoid:  wgs84
north:      2923178.04346713
south:      2890384.89306765
west:       426739.68101223
east:       500845.08464976
nsres:      2.91650217
ewres:      2.91650217
rows:       11244
cols:       25409
cells:      285698796

I am using windows 10 OS with 3.40 GHz 8 core processor and 16 GB RAM

Last edited 4 years ago by neteler (previous) (diff)

comment:2 Changed 4 years ago by neteler

Your resolution shows 2.91650217m - is this intentional? Should it be perhaps 3m or even lower?

Prior to i.gensigset it is recommended to align the computational region to the input map:

g.region raster=inputmap -p

comment:3 Changed 3 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:4 Changed 3 years ago by martinl

What is status of this ticket?

comment:5 Changed 3 years ago by marisn

Resolution: invalid
Status: newclosed

A quick calculation on a napkin indicates computational region causing memory demand larger than Windows limits. There's nothing we can do except rewrite of all signature generation code to not keep all data in memory (any volunteers?). As this option is not requested in this ticket, I'm closing it.

Original reporter - reduce size of your computational region and try again. Second option - compile a 64bit version of GRASS GIS and run it on a 64bit Windows. More information on memory limits on Windows: https://msdn.microsoft.com/en-us/library/aa366778.aspx

Note: See TracTickets for help on using tickets.