Community
cancel
Showing results for 
Search instead for 
Did you mean: 
92 Views

ippiResize_8u_C1 accessing out of bound memory

Hello,

recently some problems with ippiMalloc made me write mixed code sometimes with ippiMalloc's and sometime with simple malloc's. I know they aren't aligned, but at least they can allocate memory correctly. The same now is happening to ippiResize. An access violation is reported by MSVC and then the function returns the code which means

"Not enough memory allocated for the operation"

which I could understand if my program would be eating too much memory, but it is not. As I analyzed in the same thread of the ippiMalloc problem , there is plenty of memory left, no heap corruption (indicated by MS heap analysis functions) and, as far as I could debug, no code setting weird parameteres to disrupt all the IPP library (and I have seen this before with Ipp). Even I tried to see the assembly inside, but realized it was too much a waste of time, when it started to go into the profoundness of Windows DLLs.
So all was left for me was the same solution with the ippiMalloc problem: substitute it.
Since I still wanted functions that could do better performance, I took the Framewave version of it, fwiResize, and guess what: it worked perfectly, after 2 days struggling with all sorts of tests with Ipp. Now I'm using both libraries, which messes up with my code elegance. :)

I am compiling in MSVC 9.0 and calling my library, which calls IPP and Framewave, from a C# Windows Forms Applications. It is about image processsing, but currently I am dealing with very small images.

If someone is having the same problem or have a better solution (or hints to solve without Framewave), I would be very thankful.

Best regards,
Daniel
0 Kudos
3 Replies
92 Views

Complement: this is IPP 5.3 update 1. I'll try update 2 today, and maybe v6.0 beta to know if those bugs are solved.

Regards,
Daniel
Vladimir_Dudnik
Employee
92 Views

Hi Daniel,

could you please attach simple test case to help us reproduce that issue, as we did not see it in our internal testing?.

Regards,
Vladimir

92 Views

Hi Vladimir,

the problem was solved. Details were post in another thread: http://software.intel.com/en-us/forums/showthread.php?t=57121#53657. Memory corruption and incompatible library with IDE were the cause.

Thank you for your help.

Best regards,

Daniel

Reply