win 7 minimize and restore error

[rich937]

Hello,

This error is somewhat similar to another just recently mentioned on this board here: http://forums.ni.com/t5/LabWindows-CVI/Window-Minimize-and-Restore-issue/td-p/3085541, but not quite the same.

When running an application on Windows 7 created by LabWindows/CVI 2012 SP1, I have the problem of after the main execution window is minimized, that when it is restored the application is not responsive and I get the Windows spinning donut of doom. The application is sending commands to hardware via a USB serial port and waiting for responses. It all works fine, and many times even when minimizing and restoring the main window to open Notepad to write something down.

But sometimes, when restoring the main application window, it just never responds again. I have to go to Windows Task Manager to kill it.

In the main app, once connected to the hardware, it is reading data from the hardware to display as a graph on the screen based on a 1-10 second timer trigger.

Thanks for any help,

Rich

[inniwhoni]

Hi Rich,

Just to clarify, this problem happens with minimizing through the window button, as opposed to programatically?

Also, you said that this sometimes occurs, have you been able to observe a pattern as to when the minimization causes a problem?

Thanks,

[rich937]

Kevin,

Yes, this problem occurs with minimizing through the window button and restoring by activating from the task bar at the bottom of the desktop.

Right now, I don't see a recurring pattern. But, when it starts to occur, then it happens a lot. I've tried it on 3 different types of systems, desktop, laptop, and windows tablet. It seems to occur the most on the desktop, sometimes on the laptop, and never on the tablet.

Hope that helps some.

Rich

[inniwhoni]

Rich,

Interesting that the problem varies based on system. Could you list the hardware stack for each of these computers.

Thanks

[rich937]

Kevin,

The desktop is an HP dx5150 -

CPU: AMD Athlon 64 x2  2.2 GHz

Mem: 3 GB

Disk: 250 GB

OS: Win 7 64 bit

The laptop is a Dell Vostro -

CPU: Intel i5  2.4 GHz

Mem: 4 GB

Disk: 300 GB

OS: Win 7 64 bit

The tablet is a Panasonic CF-H2 -

CPU: Intel i5  1.76 GHz

Mem: 4 GB

Disk: 320 GB

OS: Win 7 32 bit SP1

Thanks,

Rich

[inniwhoni]

Hi Rich,

Thanks for sending those hardware stacks. The only major difference between the working and failing systems seems to be 64-bit vs. 32-bit Windows. Can you send me a screenshot of your Build Options in CVI under Options > Build Options… Also is this occurring in the development environment or with an executable built in CVI?

Thanks,

[rich937]

Kevin,

It occurs with an executable built with CVI. I have attached images of the two tabs from the Build Options window.

The distribution is being built as a 32-bit executable, since the main place it will run is on the 32-bit tablet.

Running it on the desktop is mainly for testing in the lab. But the laptop is also sometimes used with it in the field, so that one is important.

Thanks,

Rich

[inniwhoni]

It seems like the build setting are correct. When this crash happens what is the CPU usage like in task manager? Also, can you run debugging during the application and see if there is a specific line of code that the application is hanging on?

[rich937]

The CPU is not being used much.

It usually seems to be hanging up in the routine that requests data from the hardware via a timer callback. It most often seems to be stuck on ComRdTerm() function.

But, if I kill the app from the Task Manager and then connect to the hardware with a terminal program, everything seems to be acting okay.

[inniwhoni]

Rich,

You mention that it most often happens at that one line. Have you seen it hang on other lines in your code or is it always this specific line?

Thanks,