I have no C + + DLL ( no serial code / .pdb is available for c + + DLL < / Strong>) in production. It is being called by the C # application with the help of P / Away mechanism. Now, there is a leak in C + + DLL. And, after executing 20-22 times, the application crashes every time now, how can I handle this way that I continue to use C + + DLL with leak from the C # app?
For me, if this is perfect for changing / changing of C ++ DLL, and you If there is no problem in the P-Invov layer, then the only option iif's display is acceptable / em> DLL calls in an executable communication with the main one with an IPC (for example Remoting) so that you Can be forced to recycling in the hosting process. This approach will work only when you call c ++ dll, it is not very grainy. One way to do this with less effort is to host a C ++ call by cresting a web service (if calling C ++ as a web service always happens during execution) , Then host it, specify a recurring basis depending on the special appdomain and the amount remembered for it. If this is not possible, then see the solution below in your comment. Shelcher has probably been best offered.
Comments
Post a Comment