Opened 15 years ago
Closed 15 years ago
#2655 closed defect (worksforme)
runaway memory usage in _ogr.Layer_GetNextFeature (python binding), irix build
| Reported by: | mataap | Owned by: | hobu |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | PythonBindings | Version: | 1.5.3 |
| Severity: | normal | Keywords: | |
| Cc: | warmerdam |
Description
We have a python script that extracts info from a large (88M) shape file. If the script uses the 1.5.3 gdal build on irix, the memory usage grows rapidly, and without limit. (>20Gb). The problem does not occur with the 1.5.2 build on irix. It also does not occur with the 1.5.3 build on linux.
We have workarounds obviously, but for some reason there is a severe memory leak with 1.5.3 on irix.
Change History (3)
comment:1 by , 15 years ago
| Component: | default → PythonBindings |
|---|---|
| Owner: | changed from to |
comment:2 by , 15 years ago
| Cc: | added |
|---|
comment:3 by , 15 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Kicking this to the bitbucket. Reopen if there is more information.
Note:
See TracTickets
for help on using tickets.
I'm not sure if someone in the GDAL core developers has access to a Irix machine.
To help narrowing the problem, have you tried running "ogrinfo -ro -al your_shapefile.shp" (or ogr2ogr) and observing the memory usage ? It could help to be sure that the problems doesn't come from the OGR code, but the python bindings.