views:

91

answers:

1

In Visual Studio, are there any real differences between a "Release" build of an application, and a published version of the same application?

I have an ugly memory leak that's creeping up only in the published version installed via ClickOnce. The same leak does not occur in the "Release" build if I run the executable from the project/bin directory. I am very befuddled as to why this would occur because as far as I know, there should be no difference.

The application is a little involved so please excuse me for not providing more details. If it helps, the application uses DevExpress XtraForm objects and Devart (CoreLab) MySQL database objects.

edit: I must be an idiot but I tried to profile the app with ANTS memory profiler and I can't seem to replicate the memory leak. When I run the actual application Mem Usage is clearly creeping up to uncomfortable levels in Windows Task Manager but memory usage in the ANTS profiler doesn't seem to increase.

A: 

Do you know the reason of the memory leak, i.e. the reference chain form leaked object to some garbage collector root? If no, please use some profiler. For example YourKit .NET profiler http://www.yourkit.com/dotnet/

Here is the article how to find leaks in .NET applications http://www.yourkit.com/docs/net45/help/memory%5Fleaks.jsp

--serge

Serge