Dll size (debug and release)

In other discussions, I read that Release dlls have reduced size compared to Debug DLLs. But why the size of the DLL I made is the other way around: the DLL Release is larger than the Debug DLL. Will this cause problems?

+4
source share
4 answers

This will not cause problems, it is possible that the compiler "inserts" more elements into the release assembly and creates larger code. It all depends on the code itself.

Do not worry about anything.

EDIT: If you are really worried and not worried about speed, you can enable optimization for size. Or turn off auto-paste and see what difference you get.

EDIT: For more details, you can use dumpbin /headers to find out where the dll gets bigger.

+5
source

How big is your version of the DLL for release than your Debug DLL is?

Your Debug DLLs may seem small: you create PDB symbol files (so the debug symbol is not actually in the DLL file). Or if you inadvertently compile debugging symbols into your version of the version DLL.

+3
source

This can be caused by performance optimizations such as loopback - if it is significantly different, check the Release linker settings to make sure that you are not statically compiling anything.

+1
source

Performance may be affected if your application performs high-performance tasks. The release version may even be larger than the debug version if options for generating code with information about debugging enabled are checked. But it also depends on the compiler you use.

0
source

All Articles