Quantcast
Channel: Intel® Software - Intel® oneAPI Math Kernel Library & Intel® Math Kernel Library
Viewing all articles
Browse latest Browse all 3005

Memory management in vsl

$
0
0

Hi,

I am using vsldSSEditCorParameterization in debug mode (windows) and have some problems with the windows debug heal validation step, that windows always performs on de-allocation, resulting in program crashing .

If I understand properly the documentation, ("spectral") one diagonalizes the input matrix. Presumably, this is done using LAPACK. If this is the case,LAPACK requires user-provided memory to perform the task, which since I do not provide, have to assume it is allocated internally.

Then the task should clean-this up in the end, (either upon completion of calculation, or at vslSSDeleteTask ) .

Now, again if I understand this correctly, this is serviced by the mkl memory allocator, which sounds like it creates its own heap (always windows).

I do not aim to the internals of vsl, but I have this bug that is very elusive, depending on where you call the allocation/.de-allocation vsl routines from, and have been hitting it for almost a day now (this is how I actually managed to determine that it is the memory issue).

Has anyone ever had this kind of problem? 

Am I missing something?  

Should I call mkl_thread_free_buffers before vslSSDeleteTask ? - I thought one should use it in case an exception is thrown to collect the resources.

Any kind of input would be greatly appreciated.

TIA,

Petros

 


Viewing all articles
Browse latest Browse all 3005

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>