This project is read-only.


DataManager.OpenFile ignores InRam when opening Files


DataManager.OpenFile has argument InRam, but it is not passed down to the data provider so we eventually get to InRamImageData.Open where Out of Memory occurs at Image.FromFile.

Is there another way to open a large file that could be used instead?
The implementation of this feature would include passing inRam to the provider and rewriting some of the providers to pay attention to this flag.
Closed Feb 28 at 9:04 AM by jany_
This issue list is no longer active. This issue has been copied to our issue list on github (

Please check there to find out whether this issue was fixed.


vatavian wrote May 10, 2011 at 2:23 PM

One part of this problem is that we are not getting GDAL loaded as a data provider, so the default provider that uses .Net images is being used instead. I still feel that the InRam flag is being lost, but the immediate solution to our problem will be to get GDAL working.

mudnug wrote May 18, 2011 at 7:03 PM

Should this issue be closed?