Application locks up in Release build

[kerplatz]

I have a strange problem. The application I am coding in LabWindows CVI2017 will lockup after pressing a few buttons using a release build, but the same behavior does not happen in debug. How does one troubleshoot a problem like this? The problem seems repeatable, so I should be able to determine what is causing the problem. Without going into a lot of detail, I have made specific changes to my code since the last release build (it is not experiencing this error), and I suspect that is where I introduced this problem. The changes were quite extensive and it would be hard, if not impossible, to back out specific parts of this code without causing other problems. I just need some guidance on how to solve this problem.

Any help would be appreciated. Ask me questions if you want me to give details. Thanks.

[Andr3s_Br3n3s]

Hi!

Do you normally do source control? Can we compare the builds?  

Is there any way we could try to narrow down this issue? like going to specific parts of the code and comment others?

On the task manager do you see an increment of the CPU or memory when it locks?

When you mention: "  a few buttons "  that means that if you make any combination of buttons it always lock? Or you need to do a combination of steps to lock up. 

I will review all the Callbacks  of the UI to see if I am missing something. 

[RobertoBozzolo]

Since the problem can be seen in release but not in debug mode, you will want to check something that behaves differently in these scenarios.

Considering that program variables are handled differently in various modes, I'd check that "Detect uninitialized local variables at runtime" checkbox in Build options panel is marked and carefully correct the code in order to get rid of all warnings the compiler will show in build output window. You will need additionally to set the warning level to at least Common.