Opened 17 years ago
Closed 16 years ago
#1696 closed defect (fixed)
Memory leaks in MITAB driver
Reported by: | rmatsu | Owned by: | Daniel Morissette |
---|---|---|---|
Priority: | normal | Milestone: | 1.5.0 |
Component: | OGR_SF | Version: | svn-trunk |
Severity: | critical | Keywords: | MITAB |
Cc: | warmerdam |
Description
Using C# wrapper, when creating new tab files in a loop, memory usage climbs continuously.
Change History (3)
comment:1 by , 17 years ago
Cc: | added |
---|---|
Milestone: | → 1.5.0 |
Owner: | changed from | to
comment:2 by , 16 years ago
Status: | new → assigned |
---|
I have applied the mitab_feature.cpp patch upstream in MITAB (1.6.4) and will try to backport in time for the GDAL 1.5.0 release.
With respect to the mitab_imapinfofile.cpp patch, I am not convinced that it is correct. The poFeature->GetStyleString() returns a reference to an internal buffer that is freed when the OGRFeature is destroyed, so freeing it again is invalid. Unless you can provide a testcase to reproduce this leak then I am going to drop the mitab_imapinfofile.cpp patch.
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The upgrade of the MITAB driver in r13312 (GDAL 1.5.0-beta2) included the patch for mitab_feature.cpp.
Marking this ticket fixed.
Richard (by email) also suggested this patch: