Weird LabVIEW crash

I wonder if anyone can help me with a problem I am having right now.
My application has several free-running loops on the main VI (logging, UI etc etc).
I am getting strange crashes where some of the loops seem to hang, while others continue. For example a subVI will hang, and then the main UI seems to become unresponsive but the logging loop happily carries on. The logging loop does not have any UI component to it, so is it possible that I am somehow causing the UI threads to hang?
One of the free-running loops (shown in picture) updates an elapsed time counter on the main UI, this is how I know this particular bit of code is freezing. Any ideas why?
I can't really post the rest of the code unfortunately.
nrp
CLA

1) make sure you are using the latest a greatest version of the VISA driver. There was a bug in one version that would hang teh UI thread.
2) "Non-NI encoder card". If you are using dll calls to interface with that widget, check what color the node is. If I remeber correctly non-thread safe dll calls are orange be default indicating they run in the UI thread.
Just trying tp help,
Ben
Two great tips, thanks!
I will update the VISA driver asap.
You were right in the DLL calls were orange (something new I learned today, thanks again!).
I am using a (rather old) LV wrapper driver provided by the manufacturer. I see that in configuring the DLL call there is now a radio button to select whether to run the function in the UI thread or any other thread. Do you know if changing this (it was on UI thread and hence the orange node) may help or does this thread-safe behaviour need to be compiled into the DLL?
Message Edited by nrp on 08-25-2009 11:22 PM
nrp
CLA

Similar Messages

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

Labview crashes every time I click on a broken arrow (vi has errors).

I just upgraded Labview from 7 to 8.5.1 a few weeks ago. Now, when I press the broken arrow to check the errors in a vi, Labview crashes. This is a vi that was developed using the state diagram toolbox under Labview 7. I now have the state chart toolbox but not the state diagram toolbox.

Try to disconnect the state diagram from the the state diagram (right-click on the main while loop).
If that doesn't work in 8.5, try to do this in 7.1.
Or install the state diagram toolkit in 8.5.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.

Hello, LV 8.2.1 notes indicates the following bug fix:
43SAIR2A Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.
I am running this version, and still have this behavior. Is there anything I may be missing, and/or certain circumstances that may still be causing this?
thanks in advance,
Darren

Darren:
I looked at the CAR ID that you mentioned and the issue has been resolved in LabVIEW 8.2.1. To verify something similar, I ran the attached VI and things worked just fine. Please feel free to send me the steps to follow to reproduce the issue you are running into in 8.2.1.
Regards,
Rudi N.
Attachments:
MixedGraphs.vi ‏15 KB

Labview crashing - running dll. motorbee

Hi, I'm a student doing my masters project.
I'm trying to run a dc motor with the driver board and software called motorway from pc-control.co.uk
The board came with some software to run it and I have the dll. and header files.
I have managed to import the files, however whenever I try and run the "set motors" vi, labview crashes for no reason and doesn't give an error code.
The files can be found here https://www.dropbox.com/sh/0nbrx0ncyfg58y0/rKMy9iMAKE
Thanks a lot for any help as I don't have much time to complete my project!
Cheers
Henry
Attachments:
mt.h ‏1 KB

Hello, can you please post your LabVIEW code so I can look at the error in order to be able to help.
Thank you

Labview crashing when building application (exe)

Hi,
I am trying to build an application from a simple labview (2011) vi. All the vi does is sets (boolean = TRUE) a line on the digital output card (NI 9472) when I start running the vi. The program works fine after I have coded it. But when I try to build an exe file (application) of that project, then labview crashes in the build process. Is this a known issue? please help. I am attaching my vi alongwith this email
Thanks
Solved!
Go to Solution.
Attachments:
relayProject.lvproj ‏34 KB
relay.vi ‏21 KB

I'm sorry to hear that gascars. I have downloaded your project and VI and have succesfully built an executable in both LabVIEW 2011 and LabVIEW 2012. Can you please send me a screenshot of the error you are receiving? Also, can you make a simple VI that just adds two numbers and see if that can be made into an .exe.
Thanks
Chris
Chris
National Instruments
Applications Engineer

LabView Crashing and compile server error.

Hi,
I'm having some errors when I compile code for my FPGA (PXI-7831R). I am using LabView 8.2.1.
Sometimes labView crashes completely and sometimes it comes up with a compile server error.
My code contains 3 VI's. The first send sends digital output and reads digital input 10 times and then called another VI to save these results. The second VI repeats the first VI 10 times.
When the first VI is compiled on its own it works (including the saving data VI which saves it to a FIFO) but when the second VI is compiled, that is when it errors.
I have attached the compile server errors and the screen dumps of when labView crashes.
Can anyone suggest what I am doing wrong?
Thanks.

ok. Let me try and make my problem a little clearer....
I have now combined all the VI's into one.
It is supposed to write to the digital output and read from the digital outputs 10times at a rate of 10us and store the data to the FIFO. This process is then repeated at a rate of 80ms for 8 times.
I have attached a word document with an explanation on the error.
Attachments:
lvlog07-26-07-12-04-50.txt ‏3 KB
Problem Explaination.doc ‏61 KB
f623_appcompat.txt ‏93 KB

LabVIEW Crashes while closing the VI

Hi all,
I am experiencing a labVIEW crash everytime I close my VI after running it. what the VI is doing is, it communicates with an opal kelly board through the okFrontPanel.dll and reads some data from it and displays it in the front panel. The vi runs fine and I get the results as well. But after stopping the vi, when i try to close the vi, labVIEW crashes.
Has anyone faced such an issue? I would appreciate if anyone can help me fix this issue.
Thanks and regards,
Nitz
(P.S: I am not able to upload the code due to restrictions and also its a quite lengthy code to create a sample vi to replicate the scenario)
Solved!
Go to Solution.

A crash is usually an indication that something inside the DLL is touching an area of memory which it shouldn't be touching. The fact that the VI runs fine is incidental. It seems that in this case the DLL touches something which is only affected when LV needs it when closing the VI. I think the only thing you can do about it on the LV side is make sure you allocate large enough buffers for variable length parameters the DLL uses. I'm assuming you don't have access to the source code of the DLL?
Try to take over the world!

Weird OCCI crash when creating a connection

Hi Forum Users,
I wonder if anyone experienced weird occassional crashes deep inside the OCCI / OCI like the one described below, and have any clues how to avoid them?
I work in a environment where my backend server connects to a load-balanced cluster built on Oracle 11.
The server uses OCCI to connect to that cluster, the connection is resolved by service name and tnsnames.ora. The OS is RHEL5.2 running on kernel 2.6.18-92.el5 #1 SMP.
The Oracle version is: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
My server uses libraries (an excerpt from ldd's output):
libclntsh.so.11.1 => /(...)/lib/oracle_v11.1/instantclient/lib/libclntsh.so.11.1 (0x00002b4e793a8000)
libnnz11.so => /(...)/lib/oracle_v11.1/instantclient/lib/libnnz11.so (0x00002b4e7b94a000)
libocci.so.11.1 => /(...)/lib/oracle_v11.1/instantclient/lib/libocci.so.11.1 (0x00002b4e7bd9d000)
libociei.so => /(...)/lib/oracle_v11.1/instantclient/lib/libociei.so (0x00002b4e7bfcd000)
Normally the server runs fine, connecting to the database every couple of minutes.
Occassionally however, I see crashes deep inside the OCCI while creating a connection; all parameters passed to the createConnection are fine, and this crash occurs usually after a couple of days of running and hundreds of connections made; the server is a multi-threaded application so the Oracle environment object is created with the THREADED_MUTEXED type. But threads do not contribute to the issue as I have once seen the same crash at the very beginning, with the 1st connection, when there were no threads yet.
The pattern for the crash is always the same, and the application logs the parameters used in a call to createConnection before calling it and they are always OK.
Nevertheless I made several tests, passing garbage there and it never gave a crash - always an error message (even tried messing the string and using a deleted environment - always without a crash).
Weird thing is it happens so deep in the call chain, that's why I kind of doubt it is my server's failure.
Now the crash stack trace:
(signal handler calls stripped; sorry for the formatting, it's the only one I have - taken from the Oracle incident report of the ADR DIAG feature; best copy & paste to an editor that uses fixed-width font):
000000365FE0DE70 call skgesig_sigactionHa 00000000B ? 04355ABF0 ?
ndler() 000000000 ? 2AAAAC0E5BC0 ?
000000000 ? 000000000 ?
memcpy()+210 signal 000000365FE0DE70 01EED7F50 ? 2AAB300BB000 ?
000000130 ? 000000000 ?
000000011 ? 000000000 ?
intelfast_memcpy. call memcpy() 000000029 ? 2AAB300BB000 ?
A()+6 000000130 ? 000000000 ?
000000011 ? 000000000 ?
nsdo()+1296 call intelfast_memcpy. 000000029 ? 2AAB300BAF00 ?
A() 000000130 ? 000000000 ?
000000011 ? 000000000 ?
nscon()+2104 call nsdo() 2AAB300BAF00 ? 000000000 ?
2AAB300BAF00 ? 04355FF98 ?
04355ED2C ? 000000002 ?
nsdo()+1585 call nscon() 01EF74878 ? 000000043 ?
2AAB300BAF00 ? 04355FF98 ?
000000011 ? 2B5700000000 ?
nsfull_sd()+47 call nsdo() 01EF74878 ? 000000043 ?
2AAB300BAF00 ? 04355FF98 ?
04355FF20 ? 000000000 ?
nssend()+95 call nsfull_sd() 01EF74878 ? 2AAB300BAF00 ?
04355FF20 ? 04355FF98 ?
000000000 ? 000000000 ?
nscall2()+185 call nssend() 01EF74878 ? 000000000 ?
04355FF20 ? 04355FF98 ?
000000011 ? 000000000 ?
nsevdcall()+431 call nscall2() 01EF74878 ? 000000000 ?
000000000 ? 04355FF98 ?
000000000 ? 000000000 ?
nsevrec()+747 call nsevdcall() 01E07A240 ? 2AAB3009BBC0 ?
043560F58 ? 000000000 ?
01EF748F0 ? 000000000 ?
nsevwait()+3111 call nsevrec() 01E07A240 ? 2AAB3009BBC0 ?
000000020 ? 043561988 ?
000000011 ? 100000000 ?
nsevwtsg()+3185 call nsevwait() 01E07A240 ? 043561980 ?
043561988 ? 000000000 ?
000000000 ? 100000000 ?
niotns()+5611 call nsevwtsg() 000000000 ? 01EF74878 ?
12200000000 ? 000000000 ?
000000000 ? 100000000 ?
nigcall()+57 call niotns() 0435645E8 ? 000000000 ?
2B571C1444A0 ? 000000FA0 ?
01E1E2DE8 ? 01E1DEF58 ?
osncon()+1106 call nigcall() 0435645E8 ? 000000000 ?
2B571C1444A0 ? 000000FA0 ?
01E1E2DE8 ? 01E1DEF58 ?
kpuadef()+55 call osncon() 0435645E8 ? 000000000 ?
2B571C1444A0 ? 000000FA0 ?
01E1E2DE8 ? 01E1DEF58 ?
upiini()+779 call kpuadef() 0435645E8 ? 000000000 ?
2B571C1444A0 ? 2B571C1444A0 ?
000000FA0 ? 0435645E8 ?
upiah0()+36 call upiini() 000001803 ? 01EECEED8 ?
000000122 ? 000000000 ?
01E20CC90 ? 000000001 ?
kpuatch()+1399 call upiah0() 000001803 ? 01EECEED8 ?
000000122 ? 000000000 ?
01E20CC90 ? 000000001 ?
kpuspsessionget()+2 call kpuatch() 01E1DEDD8 ? 01E1ED348 ?
539 01E5C7098 ? 000000000 ?
000000000 ? 000000000 ?
OCISessionGet()+280 call kpuspsessionget() 01E20CB80 ? 01E1ED348 ?
01E50A6F0 ? 01E25F858 ?
01E5C7098 ? 00000000A ?
_ZN6oracle4occi14Co call     OCISessionGet()      01E20CB80 ? 00000000A ?
nnectionImpl14openC 1E25F85800000000 ?
onnectionEP6OCIEnvP 000000000 ? 01E5C7098 ?
8OCIErrorPvjS6_jS6_ 00000000A ?
jS6_jjS6_jNS0_10Con
nection6PurityE()+1
012
ZN6oracle4occi14Co call     ZN6oracle4occi14Co 00000000A ? 01E20CB80 ?
nnectionImplC9EPNS0 nnectionImpl14openC 01E1ED348 ? 01EF740A8 ?
_15EnvironmentImplE onnectionEP6OCIEnvP 00000000B ? 01E60EE38 ?
RKSsS5_S5_()+295 8OCIErrorPvjS6_jS6_
jS6_jjS6_jNS0_10Con
nection6PurityE()
ZN6oracle4occi14Co call     ZN6oracle4occi14Co 01E50A6D8 ? 01E60EE38 ?
nnectionImplC1EPNS0 nnectionImplC9EPNS0 00000000B ? 01E5C7098 ?
_15EnvironmentImplE _15EnvironmentImplE 043569E80 ? 01E60EE38 ?
RKSsS5_S5_()+6 RKSsS5_S5_()
ZN6oracle4occi15En call     ZN6oracle4occi14Co 01E50A6D8 ? 01E50A7A0 ?
vironmentImpl16crea nnectionImplC1EPNS0 00000000B ? 01E5C7098 ?
teConnectionERKSsS3 _15EnvironmentImplE 043569E80 ? 01E60EE38 ?
S3()+111 RKSsS5_S5_()
(some application code follow)

I am seeing the exact same behavior. Did you get a solution / explanation to your problem?
Please respond

LabVIEW crash when saving from LV2012 to LV2011 with express VI and reopen in LV2012

Hi all,
Preconditions:
Save the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" for a previous version of LabVIEW, in this case from LV2012 to LV2011
Reopen the LV2011 VI in LV2012 according to the steps below.
Steps to get it to crash:
Unzip Crash.zip
Open the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" and from there double-click (open) the "PulsedDerivative.vi" and from there double click the "Derivative dX/dt" express VI.
LabVIEW crashes!!
Alternatively when LabVIEW does not crash:
Unzip Crash.zip
Open "PulsedDerivative.vi"
Inside the VI double click the "Derivative dX/dt" express VI.
LabVIEW does not crash?
Some compiler bug?
Br,
/Roger
Solved!
Go to Solution.
Attachments:
445b4df5-fd64-49a2-8302-f8ddf06af2d3.zip ‏62 KB
Crash.zip ‏166 KB

Hi Roger,
Thank you for reporting this. I have filed CAR 390673 to our developers.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

LabVIEW crashing when running NI-DSP VI on Windows XP

I am in the process of upgrading a software application from LabVIEW 3.1 on Windows 3.11 to LabVIEW 7.0 on Windows XP with NI-DAQ 7.2. The hardware has been replaced, the relevant hardware change here is from the AT-DSP2200 to the NI-4551.
The source code uses the NI-DSP libraries to control the DSP2200. I can't find any equivalent in the new LabVIEW (and have assumed that there is none, this is all covered in the MAXX now). The source code has been convereted to LabVIEW 7.
When the source code is opened on the Windows XP machine LabVIEW crashes. I've traced to cause of this crash to the NI-DSP code. Whenever I try to open any VI that contains the DSP code it crashes LabVIEW. I think the problem is the CNI call
inside the DSP library. When I try opening the source code on a computer that doesn't have the NI-4551 installed there are no problems.
What is the upgrade from NI-DSP to? Is there a direct mapping of NI-DSP functions to equivalent NI-DAQ ones? How is it that having the hardware plugged in causes a crash even though it shouldn't be accesssed until I run the VI?
Any help would be appreciated.
Thanks.

Hello EborLance,
The NI-4551 can use either NI-DAQ or NI-DSA as the driver. If you only have NI-DAQ installed, any program that uses the NI-DSA functions may be crashing.
There is no direct mapping of NI-DAQ functions to NI-DSA functions but you can download and install the NI-DSA driver from the website. Current DSA Drivers
Once you have installed the NI-DSA driver, you should see the functionality you were previously used to and your program should run.
Thanks,
C. Flip
National Instruments

Labview crash when saving

Hi Forum
When trying to save the attached file in 8.6 (the file is created in 7.1) LabVIEW crashes with a Windows error telling me that the system has encountered a problem and needs to close.
All the SubVIs save without problems and I don't see what should cause this specific VI to cause trouble.
I have searched the forum and tried the different tricks mentioned in other threads about this issue, but none of them seems to help on my VI.
I hope that somebody has a good suggestion as to what I can do.
B.R.
Martin
Solved!
Go to Solution.
Attachments:
Crash when save.vi ‏87 KB

The problem appears to be with the typedefs. Specifically, it looks like it's the text ring. Disconnecting the typedefs in 7.1 and resaving it allows it to be opened in newer version. Attached is in 8.2
Attachments:
Crash when save 8.2.vi ‏27 KB

LabVIEW crash on startup

splash screen appears briefly, then labview crashes. I've tried a repair using the CDs but the problem persists. PXI-8110 dual-boot, I have windows and LV2011 on C:\ and Real-Time OS on D:\ I've recently been booting to RT by changing the BIOS settings, today I changed the BIOS back to boot windows, but now LabVIEW is broken. lvlog.txt copied below. What would you recommend I try next ? I'm guessing my use of the RT OS has upset something.
#Date: 23 Dec 2011 10:46:52
#OSName: Windows Vista (TM) Business
#OSVers: 6.0
#OSBuild: 6000
#AppName: LabVIEW
#Version: 11.0 32-bit
#AppKind: FDS
#AppModDate: 06/22/2011 11:12 GMT
#LabVIEW Base Address: 0x00400000
23/12/2011 10:46:55.541
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 4d84c03d-143c-4705-8479-8fae2dedb5f9
ExceptionCode: 0xC06D007E
0x01AA0EC9 - LabVIEW <unknown> + 0
0x01AA1408 - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x76E59F8E - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
Solved!
Go to Solution.

Hello,
I am unsure as to why using the RT partition was to break LabVIEW in windows unless you ran some code which made changes to the LV dependent files on the other partition. Were you accessing the C partition from the RTOS?
You mentioned you tried a repair, have you tried a complete re-install of LabVIEW in windows?
I would suggest that you did a complete re-install of all NI software. I have attached instructions and a copy of 'msiBlast' so you can do a nice clean re-install.
Let me know how you get on with this, or if you have already tried a uninstall/reinstall.
Kind Regards,
Nick C.
Cardiff University

Labview crash related to Virtual Bench 8012

My application consists of a Labview User Interface that calls a Teststand sequence.
The UI is very similar to what gets installed by default with TestStand.
In the TS sequence there are calls to VIs. Some of them are to the Virtual Bench 8012 driver.
It works well.
But when I exit the Operator Interface Labview crashes. I did debug a little bit and the crash
occurs when trying to close the Teststand Engine.
If in the Teststand sequence I skip the calls to the VB8012 driver then the Labview crash does not happen.
I am using LV2013 but TestStand2010.
Attachments:
VB8012 problem.zip ‏55 KB

I'm not having any success reproducing the issue. Here is my adapter configuration:
Here is my step settings when I call my VI:
Here is my (very simple) VI:
Zach Hindes
NI R&D

LabView crash when intensity graph is in P6 of tab control

Any available fixes for LabView crash when intensity graph is put on page 6 of tab control and right-clicked??

Michael,
This has been fixed in LabVIEW 6.1.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

Weird LabVIEW crash

Similar Messages

Maybe you are looking for