LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 2012 SP1 F5 excutable crashes whole system

Hi All,

 

 

I am facing a really strange problem. i developled an executable using LV 2012 SP1 F5. Now on two of my windows 7 system the application works perfectly fine but recently I got a new PC(in our factory) and on this new PC it doenst work. And I am not clear what the problem is.

 

What happens is that when i run the application everything works and there are no problems. but as soon as I start comunicating with my Digital and Analog cards , for the first three times the programs runs but at the third time the program hangs and also the whole windows system hangs as well till I restart the PC manually.  and the frustrating part is I donot get any error pop up or anything. I also tried using remote degugger option of whats going on but still i dont seem to find out why the first three times the program runs and then it just hangs. My last option is to install LV on the pc and run the application in debugger mode but before doing that I would like to know how else can I find out in an executable whats causing it not jsut to hand the executable but also the whole windows 7 system.

 

jsut as a small note its not a memory leak problem. this I am sure of.

 

Thanks.

 

 

0 Kudos
Message 1 of 13
(3,658 Views)

That is definitely a strange problem.  What Operating System is on the new PC?  I presume it is Windows 7, as only LabVIEW 2015 is certified to work (reliably) with Windows 10, but if it is a "new PC", it is probably Windows 10 ...

 

Bob Schor

0 Kudos
Message 2 of 13
(3,648 Views)

Let me put on my mindreader hat so I can magically take a look at the code and determine what problems you might be running into.

 

It's going to be near impossible to say what exactly you're running into.  Why are you so certain it's not a memory leak?  It doesn't sound like a crash as much as a hang.  If the system is hung, it'd make sense we wouldn't see any error windows.  You're apparently at a point where Windows is so busy it couldn't pop them up, even if you programmed them.

 

When you remote debug, do the first three attempts still work while the fourth causes a hang?  If so, where does it cause a hang in the program?  Have you used breakpoints to determine how far you can get in the program before it crashes?

 

Installing LV on that machine to debug the executable won't give you any more information than remote debugging.  If you're looking to debug the entire application, this still might give different results.  As of now, we can't determine what part of the application is causing the problem so you're better off focusing on that than you are installing LV elsewhere to get to the same point you are now.

 

Are you using any .NET, ActiveX, or DLLs in your application? 

Is the OS on all of your machines identical, to include bitness?

Do you have error handling built in to your application?

Do you have error logging built in to your application so you can take a look at the log and see the last known operation to complete?

0 Kudos
Message 3 of 13
(3,648 Views)

Hi,

 

the new pc has windows 7.

0 Kudos
Message 4 of 13
(3,639 Views)

you donot need to put mindreader hat on.

 

its not memory leak becasue my task manager doesnt show me all of a sudden high usage of memory or CPU although now when I think about the since the system is hanged probably its not updating it.

 

yes when I remotely debug the executable it crashes at the fouth time. the crash happens when I am using the DAQmx drivers. Now the tricky part is here as I am sending a digital command on one protand in the same  time I am aquring digital data on another port and Analog data from another channel.

 

yes I am usiong ActiveX but that works perfecktly fine, I already tested that part of code.

 

The OS is the same and the bitness as well.

 

Error handling is built in my application

 

Error logging is not there but I will see how can I implement it but right now I know where it hangs. Not sure why it just hangs on one PC and not the other.

 

one thing that I did find out is that the new PC has Daqmx 9.4 and my development PC has Daqmx 9.7 .....but the third PC also has Daqmx 9.4 and is working fine. Any way I will update the drivers and see if problem still presists.

 

sorry I cannot share the code becasue of company policies, not even a snipet of code.

0 Kudos
Message 5 of 13
(3,636 Views)

Did you try to use the Desktop Execution Trace Tookit from a remote system and check what is happening in the new PC?

-----

The best solution is the one you find it by yourself
0 Kudos
Message 6 of 13
(3,635 Views)

no I havents checked that I will just see online how to use it .


thanks

0 Kudos
Message 7 of 13
(3,633 Views)

after a long strugle I did get some kind of error pop up from executable. please see the picture.

 

I have no idea what it means.

0 Kudos
Message 8 of 13
(3,618 Views)

It means you were trying to access memory that you're not allowed to access.  This is usually an indication of either a bug in LV or a bug in a DLL you're using.  This is where that mindreader hat is required.  We have no idea what you're using in your application and must take your word that it's been thoroughly tested and cannot possibly be the root cause (even though signs are pointing towards this being the root cause).

 

Is there anything of value in the folder it tells you to look in?

0 Kudos
Message 9 of 13
(3,602 Views)

 I guess one problem is that the executable was made with Daqmx9.7 and the PC is running on Daqmx 9.4.

 

yess the folder that it tells me to look in has following text written.

 

Let me update the drivers and see if  this problem still happens.

 

 

and for the mindreader hat ,

 

the subvi which hangs is a simple code where I send a Digital data on one port and receive Digital data on another port and same time I also reveice some analog data from another channel.

0 Kudos
Message 10 of 13
(3,598 Views)