Auto cleanup crashes LabVIEW (and VI isn't even that large)

Hi,
I'm trying to cleanup a VI, and whenever I hit auto cleanup LabVIEW crashes and when retsrated it doesn't even say it previously crashed. I narrowed down the problem location to a for loop. The wierd thing is that I went through all the wires and objects within the loop and did auto cleanup on them but it doesn't crash. So why when I do it on all combined does it crash?
I wrote a comment in the loop that crashes to show which on it is.
I'm on Windows 7 LabVIEW 2010.0f2 32bit
I did see this posting http://digital.ni.com/public.nsf/allkb/599FB39777BDB12486257514005B7293, but even when doing it manually as suggested it still crashes.
Thanks,
Matt
Solved!
Go to Solution.
Attachments:
Score Videos temp.vi ‏126 KB

This crash corresponds to a known issue in LabVIEW (CAR #298911), which has been fixed in the forthcoming LabVIEW 2011 release. I have attached a copy of your cleaned up VI from 2011, saved for 2010. You might try to copy the block diagram into a new VI and see if that still crashes LabVIEW, but otherwise an upgrade to 2011 when it's available should clear up the problem. Hope that helps.
John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
Attachments:
Score Videos temp-1.vi ‏104 KB

Similar Messages

IMAQ Close crashing LabVIEW and sometimes Blue Screen

Hi,
I am using LabVIEW 6.0.2 with IMAQ 2.6 running on Windows 2000 OS, and am trying to get a simple ring image acquisition to operate with our Dalsa Piranha 2, 2 tap, 8k line scan camera. My problem is that LabVIEW frequently crashes (~90% of the time I run the VI), when it gets to the 'IMAQ Close.vi', and every once in a while (much less frequently) it will cause a Blue Screen. The error that I get with the crash is just a generic "Program Error - LabVIEW has generated errors and will be closed by Windows. You will need to restart the program.". The error I get with the Blue Screen is "PROCESS_HAS_LOCKED_PAGES". I have stepped into the 'IMAQ Close.vi' and have seen that the crash occurs on the 'imgMemUnlock.
vi". That VI calls the 'imgMemUnlock' function of the Imaq.dll.
Does anyone know what the 'imgMemUnlock' function of the 'Imaq.dll' really does, and possibly why I continue to get major crashes and Blue Screens. I have used the IMAQ Status.vi to monitor memory usage, and all appears well, but when I watch Task Manager instantaneously after receiveing the Program Error message box, I see LabVIEW's memory sky rocket. I've included the VI that I am using for reference.
Thanks in advance!
Attachments:
Linescan_-_Trigger_Start_Acquisition_and_Line_6.0_2.vi ‏102 KB

If I use a value less than 8192, it does work for me, without crashing at all. Thanks Katharine.
Since it's in the driver, it must mean that it is not dependent on the manufacturer of the camera then, correct? Should I expect all 8k line scan cameras to perform with the same intermittent crashing under NI-IMAQ 2.6?
Thanks again!

I have an nano 6th gen I think? And the power button doesn't work? I am very displeased with itunes:( And there isn't anywhere that services them:(

I tried to find somewhere that services them but? That's itunes for you, and the ipod, itself? I would never recomend ipods for anyone, because there isn't any place for you to get them fixed, I guess that they are just throw away cameras in the same sence, if it doesn't sharge any more, throw it out I guerss?

What does iTunes have to do with it? And where do you live? Do you have any shops that do repairs on small electronics and/or smartphones?
You can always go here: http://www.iresq.com
Or you can do an out-of-warranty replacement with Apple: https://selfsolve.apple.com/agreementWarrantyDynamic.do

So I have purchased every song on the Up All Night album by One Direction but it isn't showing up as Purchased in the iTunes store and it isn't saying that I can download the iTunes LP...help!

I bought every single song on the Up All Night album by One Direction, but iTunes is not showing the album as purchased when I'm in the iTunes store. It doesn't even have the complete my album option. It's showing as full price and I don't want to pay $12.99 just so that I can have the iTunes LP. However, I do really want the iTunes LP. What do I do?

Then you need to click the link below and fill out the email form to the itunes store about the issue
http://www.apple.com/support/itunes/store/games/

Crash LabVIEW in one click

The buggiest LabVIEW ever (8.6.1f1) keeps on giving:
WARNING: will crash LabVIEW and you will lose any unsaved work.
Open the INFO CLUSTER ctl in the attached LLB (28kB).
(Yes, I know it's ugly, I'm trying to work on it)
Right-click on the table.
Watch LabVIEW die.
Arrrgh.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Attachments:
Crash-o-matic.llb ‏28 KB

Yes, I know about the overlap stuff.
Like I said, I was working on it and re-arranging stuff on the page when I discovered the bug.
Actually, I worked around it like this:
Copied the MCListBox to a blank VI.
Created a generic property node.
Linked the property node to the MCListBox.
Set the AUTOSIZE ROW height false
Set all the row heights to 23 instead of 25.
Pasted the copy in place of the original in the control I was working on.
That's what I wanted to do via dialogs, but crashed instead.
Thanks for your offer, though.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Simulink, Labview and DLL

Hi all,
I can communicate my model in Simulink with Labview using the SIT and without working in real-time. However,now, although I have made a DLL(Dynamic Library Link) with Simulink and my compiler, I don´t know how I could run it in real-time with my target calling the DLL.
This is, instead of using my model (*.mdl) in Matlab, I want to use the DLL but I don´t know how I must call it from Labview.
If someone could help me, I would be very grateful.
Thanks
Ziman.

Hello,
considering that you have recent versions of LabVIEW and SIT, you could do that ( run the model in an RT target ) using the SIT Connection Manager ( Tools - SIT Connection Manager ). In this dialog box, you will have to select Real-Time Target, insert an IP and choose the path to the Model DLL. Once configured, then click on OK button and when running the VI, it will download the model to the RT Target
If you open an example that comes with SIT called Sinewave ( Help - Find Examples ), you will have the information to run it in an RT Target in the front panel. For more information, here you have a link ( http://zone.ni.com/devzone/cda/tut/p/id/3583 ).
I hope this helps
crisR

My Iphone 4s wont charge and it isn't the charger!

i have never had a problem with charging my phone, but recently i have been struggling to get it to charge and now it wont at all. I have tried lots of different charges and plugs and it isn't them that is the problem. I am unsure what i need to do now, because i haven't done anything wrong to it for it to start doing this!

Check for debris fluff etc in dock connector socket often the culprit
.If totally clear probably time to visit Apple genius bar
Always worth doing a
Reset
Restore
first but sounds like battery /charging system if socket is clear

Auto-save a) crashes AE and b) will not turn off via preferences

I seem to be in an endless loop of AE starting, auto-saving, and crashing.
I reported a bug earlier of AE crashing if auto-save begins during a Warp Track. I thought I could defeat this behavior by turning off auto-save in preferences, but, even with that (the save box is unchecked), auto save starts within a minute of opening a project, and freezes AE (staying at 0% Completed indefinitely).
I've deleted AE preferences, verified that auto-save is off, and the problem continues.
Any suggestions of how to defeat this would be very welcome. Thanks!

Caught in the act. After restarting, fixing permissions, reverting to a early (pre-tracking) version of the project, and verifying that auto-save is still turned off, AE tried to auto-save during a track (this time the stabilize phase) and froze.
One possible new detail - it only attempts to auto-save when the tracking footage window is in the foreground. Is it possible that AE auto-save settings do not affect the tracker when it is in the foreground? I worked several minutes without interruption in another comp before returning to see the track, and apparently triggering the auto-save somehow.
Thanks for any help.

Strange crash with Intel FFT in Windows XP x64: only when first starting LabVIEW and opening VI, not when opening VI by double-clicking

When I use the Intel FFT libraries(MKL), I seem to have a strange crash whenever I start allocating the Intel DFTI descriptors. I call a DLL from LabVIEW 8.2.1, in which these functions are used. I am working on Windows XP x64. This seems like a bug which was present in these libraries, but I got the libraries where the bug was resolved.
The strange things is that, when I open LabVIEW and then open the VI, LabVIEW crashes from the moment I allocate an Intel Dfti descriptor. But when I just double-click the VI and open it this way, I can run the VI without a crash! I already removed the DLLs in \Program Files (x86)\National Instruments\Shared\MKL\MKL70 to see if they were the cause. But even without them, I still get the crash.
I know there was a strange crash in the previous version of Intel MKL when calling a DLL and allocating this type of descriptor, so it seems like somewhere LabVIEW still uses old versions of some of these DLLs. But even then, can this explain the difference in behaviour between opening the VI through LabVIEW or directly? And if so, were could I find these DLLs? I've already searched from them everywhere.

Update:
- Opening the single VIs directly by double-clicking indeed solves the crash: from then on I can run all VIs using the libraries without any problem. So LabVIEW must do something strange when it is opened.
- Linking my DLLs statically against the Intel libraries ALSO solves the prolbem. So this seems to indicate LabVIEW loads some dynamic library which screws up everything. But only on x64 systems . This bloats my DLL, but currently I do not see another work-around.
Anyone has any more ideas? Otherwise I can always submit some test case to LabVIEW support.

Can not find size_t during import a dll and calling a function crash labview

Hello, experts
I need to use FingerLakeInstrument DLL ( see the attached) inside Labview to talk to a CCD camera. it is built from microsoft visual studio C++
I unzip FLI dll in my D:\proj\...\linfli-32 and import dll from there. created a c:\FLIDBG.txt as FLI dll needs to write debug message to it if FLISetDebugLevel() or others are called.
During importing the dll, first thing I got is <sys/types.h> ( ie size_t ) cannot be found. I have installed free version of microsoft visual studio C++
but can not find "typedef unsigned int size_t"
at the end, I just added
typedef unsigned int size_t;
in the libfli.h. Having done that, I am able to import all functions into Labview and have a user library called libfli.
However, as soon as I start calling a simple function in a test.vi, such as FLIGetLibVersion(char* ver, size_t len), which involves nothing other than the library, the labview will crash.
I created a simple C test.exe which calls many functions without any problem
any suggstion?
regards
xiaofeng
Solved!
Go to Solution.
Attachments:
libfli-32.zip ‏93 KB

Hi, Smercurio_fc
thanks for your reply. Yes, you are pointing to the right place. I have solved the crash problem.
when importing DLL into Labview using Tools\import\Shared Library (.dll), Labview automatically set the calling convention as C not as stdcall (WINAPI). it is this that later the labview crashes when a function is called. as soon as I manually re-selecte calling convention as stdcall, my test.vi works OK (see attached).
I tried Call Library Function too to call libfli.dll, as long as I select stdcall as call convetion. the test.vi works.
How do I know which Call convention I need to choose if there is no infomation from DLL provider?
as for the size_t,
I add #include <crtdefs.h> in libfli.h and
add additional include path as
C:\Program Files\Microsoft Visual Studio 10.0\VC\include. this solved the "not found" issue.
for this case I know that the DLL is built from VC++, is this right way?
again, thanks for your time.
xiaofeng
Attachments:
test.vi ‏13 KB

File dialog crashes LabVIEW 2014 on Mac OSX Yosemite

I know that Mac OS 10.10 (Yosemite) is not technically supported by LabVIEW 2014. If that's the only answer to this question, then so be it.
The following causes LabVIEW 2014 to crash on Mac OSX 10.10 (Yosemite):
1. Run the native File Dialog in LabVIEW 2014 (Express VI) , using "New or Existing File" as the selection mode
2. Select "New File..." when the file dialog appears
3. Enter anything as the file name and click OK
4. LabVIEW either crashes immediately, or hangs indefinitely and must be force quit.
Is there an update for LV 2014 (and the RTE) that does support Yosemite?
This bug makes deploying apps to the Mac basically impossible, Yosemite is the latest OS. Does anyone have a workaround for the issue?
Thanks.

LabVIEW 2014 SP1 seems to solve that problem here on my Mac OSX 10.10 system.
Now Apple may be nice for end users, but all those Apple fan boys sure would think a little different about it, if they had to write programs on the Mac. Apple keeps changing its APIs and their behaviour continously, inventing new APIs (which is fine) in a rapid pace, only to depreciate and remove older APIs at almost the same speeed!
Microsoft sometimes goes to the other extreme with maintaining backwards compatibility but working with Apple systems surely isn't easy as a programmer (unless maybe when one uses their high level click and point together web design applications, but I don't know that).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Save for previous version 8.5 to 8.2 generates code that crashes Labview (uses classes)

Hello,
I'm working on some java style interfaces for labview for hot swapping of instrumentation for design patterns. When I try to port this code, developed on Labview 8.5 back to labview 8.2, the code it generates crashes labview (both 8.5 and 8.2).
Included is a small snipet of the work that demonstrates this behavior.
It includes to classes:
untitledProject1 - the containing project (version 8.5)
FunctionGeneratorI - Similar to a Java style interface (A class with all Dynamic VI's with no useful functionality)
FunctionGenerator33220a - An intended implementation of Function generator (only a few functions implemented)
and a folder "labview8_2Distribution"
Which contains the port of the 8.5 code to 8.2.
To recreate the error:
A.
1. Open "labview8_2Distribution\Users\Laptop\Desktop\object\Untitled Project 1" (8.2 save)
2. Verify it crashes labview 8.5 and labview 8.2.
3. Watch labview crash?
B.
1. Open the "Untitled project 1" in the root directory. (Using labview 8.5)
2. Save the project as a labview 8.2 type.
3. Try to open the saved version with 8.5 and 8.2.
4. Watch labview crash?
Greg Sonnenfeld
Attachments:
error.zip ‏885 KB

Hello Karunya,
In regards to your questions:
>Can you post your code? Have you tested this by creating another project?
Do you have an xcontrols in your projects? Do you have typedefs? Do you
have a LVOOP constant on your block diagram? Are you also using Classes?
I cannot post the cost as it is way too big. Not really my code but a spaghetti code from a previous programmer. I think problems saving it to a previous version have to do with a few things:
1) Memory - I have 1 GB of RAM and I am running XP. I notice the available RAM dropping quickly as it is saving and then it blow up.
2) Long Filenames - The directory path of the original file is incorporated into the saved "previous version" of the code. While a good design, it does make the file/path a bit longer when saving
3) One of teh things it saves is the drivers and their menus. This is due to the drivers being in a subdirectory of the original code and not in the c:\program files\national instruments\labview 8.5\instr.lib directory. I saw this when I tried to save the file as an LLB.
4) If I work with smaller parts of the code without long paths, it saves fine.
There probably are xcontrols, definitely typedefs, no LVOOP's or Classes. Hope you can do something with all this. It just seems that converting to a later version of the code should be reversable. Thanks.
Michael

Implementing Auto Contract Generation/Negotiation and Execution

Would love to hear from anyone that has implemented auto contract generation/negotiation and execution. Were there any lessons learned you could share during implementation? Were there things you found out - too late? Are you seeing adoption? How long did the implementation take? Pain points along the road? Things you would do differently? We are getting ready to take this trip ourselves and I have a feeling it will not be smooth sailing.

Hello Sravan
Your message isn't clear fo me
If you used import for new master data you can use automatic key generation ability for inbound port
The another way:
You can create special key field in MDM and
create simple workflow which fire when ADD record.
That worklflow call assignment which fill key field
Regards
Kanstantsin

Vision Builder Crashes Labview

I have an application where I need to acquire and inspect many high resolution images 3Mp at high throughput.
I'm using:
LabVIEW 8.5.1
NI-Imaq 4.1
Imaqdx 3.2
Vision Builder AI 3.6
ISG 3Mp Camera through Startech 1394a PCI card
In order to meet the cycle rate, I'm trying to multi-thread the application by having one thread that acquires images and enqueues them into another thread that saves them to the hard drive then runs the VBAI inspection. The VBAI inspection then uses the "simulate acquisition" step inorder to load the image from the hard drive and make the appropriate measurements. I've run the application and monitored the processor usage, and the processor seems to stay within 0-80%. However, my application will crash intermittantly.
I've been able to repeat the behavior pretty reliably if I activate/toggle a ring control on my front panel while the cycle is running, and I can't do so if the VBAI thread is not running.
I understand that this is could be a difficult problem to help debug remotely. I'm wondering if there is anyone with similar experience, or some better way for me to creat a high throughput machine vision app with VBAI.
Thanks,
Ryan

Dear Ryan,
You are right, this is difficult to debug remotely, but I can make a suggestion or two. Perhaps you've taken care of these, perhaps not...
One potential downfall with this setup is running into a race condition. If you don't establish data dependency, and make sure that you save and close a particular image before trying to open back up again with VBAI, you could cause the behavior described. Race conditions would be even more of a concern if you were using a certain number of files as an image buffer, and then recycling through them.
What in this ring control? What does the ring control do?
Have you tried generating LabVIEW code from your VBAI inspection, and then encapsulating the VBAI code in a subVI, and just passing your images into that instead of saving them to disk? I would suggest doing this to see if you still experienced the crashes when you are only working in LabVIEW, and without saving and opening images from disk.
Let me know how things go; I hope the above suggestions provide some help.
Best Regards,
~Nate

Passing control reference to subVI crashes labview

Hi,
using a image control (as indicator) provided by imaq Vision, I tried to pass the reference of the control to a subVI. On a computer it works and on a other (same labview version, same vision version, same os, same hardware and hardware drivers!), this crashes labview. I tried to close the control refnum at the end of the subVI, but that changed nothing to the issue. Now I use the reference as a global variable and it seems to work...nevertheless, I would like to understand what the issue and if I should remove any passing to subVI of control ref because this can potentially triggers an error. My correlated question is if this global passing is a "fake" workaround or have real chance of improving (this before going through the whole code for changing all passing of reference to subVI)
thanks a lot

Hi,
thank CoastalMaineBird for your answer
How do you know it's this issue which causes the crash?
When I remove this parameter from and the only property node in the subVi that write to it, I have no longer any problem. Moreover, to ensure that's really the "passing", and made a global variable containing the reference to this control and use my original SubVi that do access the control through its reference number
, and it works! In this last exemple, the only change is the way of transmitting the reference
What LabVIEW version?
8.0.1
up to date according Measurement & Automation update tool
Given that one computer works OK, and another crashes, I would say that
you are seeing the effect of something else, not the cause. If passing
a control ref via terminals was fatal, it would be fatal all the time.
You have some other sort of issue, perhaps timing of the different
machines triggers the bug, perhaps running out of memory, perhaps
LabVIEW is corrupted on one machine.... But I don't think changing all
your code to use globals would solve the real problem. Actually, saying that I wonder about problem of synchronisation. I know from Visual C++ that this kind of error happens if two process try to access the same control at the same time. This is typically an error changing from a computer to an other, and mutex or semaphore are the way to deal nicely with that. But does labview contains already such a securisation? If so, the global variable point on a single object and can "fell" the semaphore/mutex. But passing make a copy that will likely have two different semaphore/mutex but will point to a single control! Do someone know if I'm wrong in this idea or not?
Thanks

Auto cleanup crashes LabVIEW (and VI isn't even that large)

Similar Messages

Maybe you are looking for