Debugger crashing after F5

[sivanov]

Constantin,

I resolved the issue by using dynamic linking  for my dll with windows API instead of static by adding the .lib to the project. This is a bit strange...

Stan

[ElectroLund]

It's been a while since my debugger crashed.  But it did just now and I finally got a chance to run your application.  I got no windows in red:

[Constantin--P]

Hello Electro,

Your windows seem to be from LabWindows/CVI. You should enter the process ID of your program (the one you are debugging with CVI).

Since you said WebBrowser.prj doesn't have the problem for you, the cause of the hang could be different in your case but it's worth a try.

Constantin

[ElectroLund]

Ah, of course.  My mistake. 

While I wait for another crash, I've been seeing these dialogs (one after the other) frequently when starting the debugger:

Are these related to this discussion or not?  For what it's worth my Execution Profiler output looks pretty good in terms of process load:

[sivanov]

Do you use the output queue with your com ports? If so and can disable it, set the output queue length to -1 in opencomconfig...

[ElectroLund]

Mine is already set to -1 (immediate write).

[Constantin--P]

Hello Electrolund,

These dialogs are normal to appear after you kill the debugger. Because you manually killed it, CVI is in a bad state.

Do you see the dialogs after you restart CVI?

[ElectroLund]

I think you're right.  After a restart, I don't think I see those anymore.  I'll pay more attention next time.

[Constantin--P]

Hello all,

The issue should be fixed in LabWindows/CVI 2015 f1 patch.

Have a nice day,

Constantin