Hi,
we have a rather big .Net-Solution using GdPicture-components. We have some problems getting enough memory (in one piece) for decompressing our images (tiff / jpg).
One solution could be, to make our program LargeAdressAware, so we could use more than 2 GB of virtual memory. Do you see any problems
using your dlls in such an environment? Problems might occur in unmanaged code, in old c-libraries etc. i.e. casting an integer to a pointer...
At the moment, we use GdPicte Version 7. We use:
GdPicture.NET.dll, GdPicture.NET.image.gdimgplug.dll, GdPicture.NET.pdf.gdpdfplug.dll
It could be an idea to upgrade on version 8, but we do not really have the time at this moment to do that, anyhow, would your answer differ, if we would upgrade?
Then we would use in version 8:
GdPicture.NET.dll, GdPicture.NET.PDF.dll
Can you give me a statement on this topic please?
best regards,
Oliver
LargeAddressAware-dlls
Re: LargeAddressAware-dlls
Hi Olivier,
I never tried the LargeAdressAware option with our 32 bit assemblies. I just can suggest you to make a try.
In GdPicture source code, we never cast integer to pointer and vice-versa. In fact, we never cast anything except for inherited objects.
Kind regards,
Loïc
I never tried the LargeAdressAware option with our 32 bit assemblies. I just can suggest you to make a try.
In GdPicture source code, we never cast integer to pointer and vice-versa. In fact, we never cast anything except for inherited objects.
Kind regards,
Loïc
Who is online
Users browsing this forum: No registered users and 1 guest