All along, earlier this week, I was fighting a MemoryAccessViolation at the
time of calling cmsDoTransform(HANDLE, InputBuffer, OutputBuffer, Size).
Then I started experimenting with very small images, like 1 pixel wide x 1
pixel high.
All of a sudden, the MemoryAccessViolation was gone!
So I used larger and larger image sizes, 4x4, 16x16, 64x64 -- everything was
working.
So I went back to my original RGB test image, 864 pixels wide x 288 pixels
high, and BANG!, that MemoryAccessViolation again?
So I decreased the image size down progressively :
1 - 288 x 288 -> didn't work?
2 - 256 x 256 -> didn't work?
3 - 128 x 128 -> Victory!!!
The image size is 48 kilobytes, thus passing 49,512 bytes in memory to
cmsDoTransform.
Maybe there is a buffer size built-in "upper limit" that can be managed by
.NET?
I hate to have to break the image in chunks...
Best / Roger
|
