LabVIEW IDE crashing!

Hi there,
I have just run into some very strange behaviour in LabVIEW (7.0 on Win2k with service pack 2).
I have an event structure with several user events (about 12) listed in it. Everything was working fine yesterday. Today I tried to add another user event to the structure and LabVIEW crashed (giving usual cryptic error message saying referenced memory could not be read).
Now, I have experimented quite a bit, and have the following observations to give:
LabVIEW is happy adding more events until I try and add an event if the currently selected event is a Filter event (i.e Mouse Down?).
I have a certain Mouse Down? filter event, and if I change this to a non-filtered Mouse Down event then LabVIEW lets me add more event cases as normal. However, I need this to be a filtered event (i.e with the "?"), and in this case, the next I try and add results in the LabVIEW IDE crashing. I can add more events as long as I dont have a filtered event case currently selected, so I suppose this is a work-around.
To clarify, this occurs when I am trying to add events at design time, not at run time.
I tried to replicate this in a new VI, and everything works fine as expected :-(
I can't really attach the VI.
Has anybody else noticed behaviour like this???
nrp
CLA

hi there
thanks for your suggestions
>> A couple of suggestions:
>>1. Try opening the VI on a different computer\LV version.
>>2. Try copying all the code in the VI into another VI and see if this still happens.
>>3. Start deleting pieces of the VI until it stops (or there is nothing left).
I tried options 2 (same crash) and option 3 (crash stops when I delete the Filter events) before I posted the question.
I have tried opening the VI on another PC (also Win2k) with the same version of LabVIEW and it also crashes.
sigh...
I suppose I am just going to have to work around it for now... strange bug...
nrp
CLA

Similar Messages

Opening VI forces LabView to crash - How to reconstruct data of the VI?

Hello,
as explained in the subject LabView crashes. This means if I open the VI the LabView project just disappers. I would like to reconstruct the internal data/programming of the VI? How can I do this?

Another option is to drop the VI in another VI.
If all fails contact your local NI representative, they should have tools to recover from such issues.
It might help to repai LabVIEW
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 8 crashes when saving a vi with a 'Bundle By Name' function

We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.
Trying to open this vi with Labview 8 crashes Labview.
Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.
Any ideas would be a help.
Attachments:
Labview_Upgrade_Crash.zip ‏117 KB

Sorry for the delay, I have been testing on other machines.
We can reproduce the error on other machines, with completly fresh installs of Labview 8.
The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.
I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.
When the COM Server is installed, Labview 8 crashes when opening the vi.
I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).
I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.
It will not install any other files on your computer and, can just be deleted when you are finished.
Thanks
Charlie.
Attachments:
COM_Server.zip ‏659 KB
Labview_Upgrade_Crash.zip ‏117 KB

LabVIEW is crashing when i am trying to build the exe

I am trying to build an executable from a program in which i am communicating with several instruments, whenever i am trying to build an exe labview is crashing and i am getting the error Exception: access violation(0xc0000005)at eip=0x10054DD1.
after reading some posts on forum i tried builduing an exe on other system also, but still i am getting the same error.
below i am attaching the program and the image of the error i am getting.
Attachments:
labview crash.png ‏53 KB
automation.zip ‏4455 KB

Ritu wrote:
waiting for the reply....
Realize this community is by a large majority volunteer based. If you need urgent support contact NI directly
http://sine.ni.com/apps/utf8/nicc.call_me?loc=en-US
That being said I would try to disable the large amount of code. Say you have a Main that launches a bunch of stuff, put a disabled diagram code around the launching part and then try to rebuild. It is a very slow process (especially when the build takes a while to fail) but by doing this you can more isolate the parts of the code that can cause the crash. The only time I've seen a crash on build like you described, I simply rebooted and it was fine. Usually because of my own fault by stopping code in a bad way previously leaving things in memory.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

Running the VI causes LabVIEW to crash

Hello
While debugging a SW, I found that a particular VI, when run, causes LabVIEW to crash. This happens whether this VI is called while executing an exe or called by higher VI or even when it is run separately.
The VI to be run is NLD_Test_PP_Plot.vi present in the folder "Generic VI's".
The input for this VI is .csv file, which is attached. The csv file needs to be placed in a separate location and that path needs to be entered in the string constant in the VI.
Note: This VI is developed and run in LV v2009.
Thanks
Sharath
Attachments:
SpecimenCW_20150407_193059.csv ‏67 KB
NLD_Test_PP_Plot Folder.zip ‏208 KB

LabVIEW did not crash for me (nor did it throw an error). It made a bmp of your data and then exited. I am using LV 2013.
Did it actually crash or did it throw an error? If it crashed, do you have the crash zip file?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Deny Access function with invalid file refnum causes LabVIEW to crash

Hi folks,
I have LabVIEW 8.5, and today encountered something interesting that consistently causes LabVIEW to crash. Essentially, if you find the "Deny Access" function under the advanced file IO palette and wire up an invalid refnum, Windows (XP in my case) reports that LabVIEW has to close. I checked in task manager, and the LabVIEW process is still active and using a disproportionate amount of the CPU.
To reproduce the issue, simply drop the function on your block diagram, create a constant from the refnum input terminal, and run the VI. Has anyone else seen this behavior?
Thanks,
Jim

Hi Carla,
I'm glad to help, and thanks for looking into it. The way I ran into the bug was while I was working on an action engine VI to log certain text values (see attached picture). While logging, I didn't want other programs to access the file. When a new file had to be generated, I wanted to stop denying access and close the reference. However, if the value on the shift register was invalid, LabVIEW crashed instead of throwing an error (I guess a crash qualifies as an error).
If you look at the attached picture, my workaround was to use the "Not A Number/Path/Refnum?" function. If the reference is bad, I don't try to use the "Deny Access" funtion or close the file. That worked just fine and seems like a good solution for now.
Jim
Attachments:
Logger.png ‏6 KB

Picture in a Comment on the LabVIEW Idea Exchange

How do you post a picture in a Comment on the LabVIEW Idea Exchange?
Richard
Solved!
Go to Solution.

altenbach wrote:
Broken Arrow wrote:
How do you post a picture in a Comment on the LabVIEW Idea Exchange?
Submit the comment without picture, the edit it.
Once you edit the comment, you have the full editor, including the "attach" button.
Now attach the image and submit the edited comment.
Now edit it again and embed the attachment (you only see it whe editing).
Do all this quickly so you don't run out of time.
Laura,
Since the last forum update, we can no longer attach anything when editing an idea so these instructions are no longer valid. Can we have the old functionality back? Please?
Thanks!
LabVIEW Champion . Do more with less code and in less time .

Labview 2013 crashing when restarting VI

My VI runs and I have no problems.
If I stop then Vi and re-run it, pretty much every second time it crashes. It does not point to anything and the only message I get is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 13.0.0.4051
Application Timestamp: 525595c6
Fault Module Name: NiViPxi.dll
Fault Module Version: 5.4.0.49152
Fault Module Timestamp: 51c243ad
Exception Code: c0000005
Exception Offset: 0000bbe0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 6153
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This only clue in the above I can find is NiViPxi.dll
I am using a PXI rack so maybe it is to do with one of the devices?
I would be nice to have more clues, does anyone know why labVIEW keeps crashing?
Rgds,
Sean
Solved!
Go to Solution.

Hi jinfone.t
I managed to root cause it to a netway 72 PXI dll and have fixed the issue, (took a lot of effort!)
- Does the crash only occur when you re run this particular VI that you are talking about?
Yes
- Is there any crash logs generated?
None that I know of apart from the output I pasted on the screen. It's possible there is something in the event monitor
- What does your VI do?
It function tests our product, (IOT)
- Would it be possible to show the code?
I'm afraid not as it is proprietary. However, the issue appears to be due to the dll. Netway may release the VIs but I believe you are required to buy hardware/ software.
The issue I have is that LabVIEW is not handling this crash well at all. It does not point to the problem dll nor does it drop a fail log that I know of.
Thanks for the feedback.
Ciao,
Sean

Labview 2014 crashing(windows 7)

Hello for some reason my labview 2014 crashes when i try to open the labview application. It was working fine until yesterday but not having any luck today. Also i cannot see my labview software in the programs and feature section on the control panel even though i have administrative privileges in my computer. I have attached my error report below.Any help would be appreciated.
Attachments:
crash_report.PNG ‏109 KB

Hi go_sa,
In Programs and Features are you looking under National Instruments Software for LabVIEW 2014? If so, and LabVIEW is not listed, have you tried re-installing the software?
If it is listed under National Instruments Software, it sounds like there may be some software corruption causing the error. The next step would be to try repairing the program. If this does not work, you can try force re-install the program (link below) or uninstalling and reinstalling it.
http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79
Julia P.

Adobe Ideas Crashes and no Adobe Draw for Iphone...

Adobe Ideas Crashes and no Adobe Draw for Iphone...I just receive a email stating there will no longer be any support for Adobe Ideas which is fine if you have an alternative which would be Adobe Draw. Now problem number 1 Adobe Ideas is crashing so with that being said we can not use it even if we wanted to being that is the only vector app you offer for the iphone. Adobe is giving a deadline of November 21st. I think Adobe should at-least fix the issue before stating a deadline with adobe ideas or release us a version of Adobe Draw for the iphone this is very frustrating for a long time Adobe users of the apps and programs..you drop the ball on this one ADOBE. very disappointed.

Wish I could help offhand but I'm on Android (which doesn't have Ideas anymore). Ideas produces vector files, no? Someone at the App Store site mentioned you can open the files produced in Ideas in something like SketchBook Pro (which can, in turn, produce raster file formats like PNG, JPEG and PSD).

Adobe Ideas crashes directly by starting...

why? and how can i fix this problem to start the app "adobe ideas"? I use an iphone 6+ 128 gb....

Same issue. I hope they address this problem soon. This is the only good drawing app for iPhone and I am going crazy over here!
• Adobe Ideas crashing on startup
• iPhone 6+
• iOS 8.1 (current OS)

"Using a CIN to Create an Array of Strings in LabVIEW" example crashes LV on Linux

Tried to utilize this NI example: "Using a CIN to Create an Array of Strings in LabVIEW" (http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B4B282BE7EF907C8E034080020E74861&p_node=&p_source=External)
Compiles OK with the makefile made by the LV's lvmkmf utility. Nevertheless when I try to run the VI (with the code loaded into the CIN, of course), LabVIEW 7.1.1 on a SUSE 9.3 Linux machine crashes:
LabVIEW caught fatal signal
7.1.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0
Segmentation fault
Any ideas? Did anybody try this on a Windows machine?

H View Labs wrote:
Tried to utilize this NI example: "Using a CIN to Create an Array of Strings in LabVIEW" (http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B4B282BE7EF907C8E034080020E74861&p_node=&p_source=External)
Compiles OK with the makefile made by the LV's lvmkmf utility. Nevertheless when I try to run the VI (with the code loaded into the CIN, of course), LabVIEW 7.1.1 on a SUSE 9.3 Linux machine crashes:
LabVIEW caught fatal signal
7.1.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0
Segmentation fault
Any ideas? Did anybody try this on a Windows machine?
This code is badly broken. In addition to resizing the actual handle to hold the number of string handles you also would need to create the string handles itself before attempting to write into them. NumericArrayResize is the fucntion to use as it will either resize an existing handle (if any) or create a new one if the value is uninitialized (NULL).
/* resize strarr to hold handles to NUMSTRINGS strings */
err = SetCINArraySize((UHandle)strarr, 0, NUMSTRINGS);
if (err)
goto out;
/* perform this loop once for each element */
/* of array of strings being created */
for (i = 0; i < NUMSTRINGS;) {
LStrHandle handle = (*strarr)->arg1[i];
/* determine length of string that will be element of strarr */
strsize = StrLen(str[i]);
err = NumericArrayResize(uB, 1, &handle, strsize);
if (err)
goto out;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/* moves strsize bytes from the address pointed to */
/* by str[i] to the address pointed to by the data pointer in the handle */
MoveBlock(str[i], LStrBuf(*handle), strsize);
/* manually set size of string pointed to by *strarr */
(*((*strarr)->arg1[i]))->cnt = strsize;
/* manually set dimSize of strarr */
(*strarr)->dimSize = ++i;
return noErr;
out:
return err;
Rolf KalbermatterMessage Edited by rolfk on 06-30-2005 03:15 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Labview 8 crashes when using Read Labview Measurement File

Hi All,
I am a new user for Labview. I installed Labview 8.0 from the CD (evaluation copy). I was just testing the sample code provided by NI. I opened the "Load from File and Display" example and I was trying to open the properties for the Read Labview Measurement File component when Labview crashed. I tried it a couple of times and everytime it happens the same way (when I double click the component or right click on it).
I am using Windows XP with all the updates done. In the Windows crash report, the application version is 8.0.0.4005.
Other problem I encountered is a missing component on the Input Palette (no DAQ Assistant present) and the Instrument I/O Assistant raises the error "Measurement & Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from the Labview Driver CD". For the last problem, I will try to run the Labview Driver CD, once I get it. But I am not sure if the DAQ Assistant will show up then or not.
Any ideas?
Regards,
Nick

Hello Nick,
While it is not my area of expertise, I would expect the DAQ Assistant would appear after installing the driver CD as you said you would be trying.
What caught my attention was the crash. The easiest way to resolve the crash is to delete the instance of the Read LabVIEW Measurement File on the diagram and place a new one from the Express Input palette (now called "Read From Measurement File"). In that situation, I would expect just pressing OK to accept the default configuration should work. The crash occurs in certain circumstances when the Read / Write Measurement File Express VIs are dropped from a previous version of LabVIEW and then their config page is opened in 8.0.x. This issue should be resolved in a future release, sorry for the inconvenience.

LabVIEW program crashes after running for few hours

Hello,
I am doing some experiments at the moment which are supposed to last for 18 hours.
Basically, I use a LabVIEW program to control a power supply through a LabJack U6 DAQ. I am currently using LabVIEW 8.5 on Windows 7.
In order to do that, I use a laptop where everything has been disabled such as power management settings, network access is off, windows updates are also off...
As far as I know, the computer can't turn into sleep mode or just shut down (I'm a 100% sure of that actually).
But last night, I started an 18 hours experiment at 5 pm, and when I came in this morning, the program shutted down by itself. Fortunately, the power supply is still providing the voltage I want, but I can't figure out why the program crashes.
When I start the experiment, it also automatically starting saving data in a spreadsheet file (I guess the size of the file should be 36 MB), so it might be a problem of memory access or something.
I really don't know what could have cause this crash, does someone have an idea?
I saw some other threads similar to my problem but I am not running an executable, I am running the front panel directly from the editing mode.

Hi,
thank all of you for your quick answers!
@Josborne : I do not have an error handling in my program. Actually you can look at my program in the attachment file. This is my first LabVIEW program so I've never dealt with error in and error out function... Moreover, what is a log file exactly?
@Johnsold : Yes, I am building an array continously growing over time. Actually, my program stops saving data when you hit the "STOP" button, it doesn't write into a spreadsheet file through a period of time, that is something I eventually need to correct.
@LabJackSupport : I can try to reduce my time step, so far it's 100 ms. I have a problem with disconnecting the USB cable from the computer though : for no reason, if I just unplug the connection between the LabJack U6 and the computer, my power supply will just go providing 157 Volts! And for my experiment, this is something we don't want to have so we just leave it as it is now. Disabling some part of the program is a good idea, I can try it
Thank you for your answers
Attachments:
Control Software.vi ‏511 KB

LabVIEW IDE crashing!

Similar Messages

Maybe you are looking for