Access violations with GDALDataset after writing shapefile

[rhaden]

An application I've been developing requires the capability to write "flagged" features out to a shapefile. However, function calls to a GDALDataset object after successful shapefile writing can result in access-violation exceptions.

The conditions under which these exceptions occur seem to be the converse of those listed for the issue in ticket #4549. That is, if calls to OGRLayer::CreateFeature() are successful, then calls to GDALDataset functions are not (and vice-versa).

I'm honestly not sure whether this is an issue with the C# bindings to GDAL or with the underlying C/C++ GDAL code.

[Even Rouault]

I'm closing this one as a duplicate of #4549. I can't see a relationship between OGR and GDAL world. It is likely a memory corruption in OGR that causes unrelated crashes later

[rhaden]

No problem. I wasn't sure how many tickets I should create, so I figured too many was better than too few. :)

[Even Rouault]

Well, think to the poor GDAL subsystems mainteners that have not necessarily a lot of time to spend to admisitrate Trac... So unless you are pretty sure the issues are different, it will not speed up the resolution...