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 

Similar Messages

  • Labview crashed when saving vi and now cannot open VI libray

    Hi
    I am using LabVIEW 7.1.
    I am developing a moderately large application.  I Just saved my main VI and LabVIEW crashed for some reason.
    My vi library will now not open.  When I try to open the library I get the error message: "an error occured when listing the contents of (my directory/myvi.library)".
    Has anybody ever had this problem and if so does anybody know how I can recover my vi library?
    I have just lost about 2 days work so if anybody has any ideas I would be most grateful.
    I hope it is not a fatal problem - I cannot even show the vi's in the vi libray using windows explorer.
    Many thanks
    Ashley

    It looks like you've learned the hard way why you should not use .llb's
    during development. If a single VI in the library get's corrupted, the
    entire library is bad. This is why during development, you're much
    better off keeping everything in an organized directory structure. This
    way, a crash like you had would only affect those VI's that had not yet
    ben saved.
    I've heard rumors that NI has an internal untility that might be able to recover the library. I'd try contacting support directly to see if they can help.
    Good Luck
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • 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

  • How do I resolve CS4 documents from crashing when saving or checking in stories with InCopy?

    We have been having a persistent problem with InDesign CS4. After creating certain documents (off templates), they seems fine for hours, even days, but eventually, the time it takes to save increases and increases until eventually InDesign crashes. Though the work is recovered when the program restarts, attempting to save still causes the program to crash. The same crashing problem happens when trying to check in stories that have been placed using with InCopy. We have reset preferences and coordinated all the versions and serial numbers on our network to eliminate any conflict. Is there anything anyone can suggest? This has been goign on for more than a month and is seriously slowing our production cycle.
    Thanks,
    -AB

    First, on the black bars.  I do not want them at all.  I cannnot post a screenshot now as
    file attachments are turned off temporarily, but they are about 5% on either side.  Totally unacceptable especially when in CS3 when exported to Encore there are NO black bars either visible in Encore or in the resulting DVD's
    On the options and is the preset saved.  I can close Encore and open it afresh and find the preset that I saved listed in the dropdown of presets with the name I saved it as and all the settings the way I want them.
    On the issue of Transcode settings when selecting the resource...  When I select the resource in the Project panel, or in the Timeline tab, the Transcode settings is greyed out.  I have consulted the help screens and forums for various ways to change the transcode settings and none of the suggested ways work.
    It looks like my CS4 install does not work the way yours does.  I am about to completely unistall CS4 and CS3 and all other Adobe products and try a fresh reinstall to see if that works.  Most likely I will simply reinstall CS#, since that works, and abandon CS4 for now as I am getting way behind on my work, and know I can finish with CS3.  I have also heard form others that Sony Vegas is really solid and does not have all these weird bugs such as seen in CS4 and CS5, and is a much less bloated product and does the encodings faster.  Since it is also less expensive, this seems too good to be true, but work a trial.  So first rip every Adobe product off  my PC and format the HD and start fress with JUST CS3 and get my work done.  Then try Vegas to see if it is as good as my buddies say, if so bye bye Adobe!

  • 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.

  • Mail crashes when trying to attach a filename with both Hebrew and English

    Mail.app crashes when trying to attach a file whose filename has both Hebrew and English characters in it.
    This even happens if the file is first zipped!
    Any temporary solution/workaround until Apple fixes this bug?

    This report is about the Flash plugin:
    *bp-f13d802e-81d7-48fb-b101-ecdd22130310 3/9/2013 8:00 PM
    Make sure that you have the latest version of all plugins.
    *http://www.mozilla.org/plugincheck/
    *http://www.adobe.com/software/flash/about/
    *http://www.adobe.com/special/products/flashplayer/fp_distribution3.html
    You can check for problems with current Flash plugin versions and try these:
    *disable protected mode in Flash 11.3 and later
    *disable hardware acceleration in the Flash plugin
    *http://kb.mozillazine.org/Flash#Troubleshooting
    *http://helpx.adobe.com/flash-player/kb/flash-player-113-crash-mozilla.html

  • Labview crashes when 16 bit images are sampled with 1394 camera

    Hello! We are using a Basler A102F camera and when we use the 16 bit format Labview is crashed. There are no problem when using the 8 bit format. It crashes also when using the scalable mode (full camera chip). We are using "Grab.vi" in the program.
    There are also some problem when using MAX and these formats.
    Please help us.

    Some combinations of settings are not valid for cameras. I would make sure the combination you are using works properly in MAX before trying it in LabVIEW, because if it doesn't work in MAX it will never work in LabVIEW.
    Check the camera manual and see if the combination you are trying to use is valid. I suppose some settings may not be compatible with the IMAQ firewire drivers even if they are valid to the camera, but I'm not sure.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • Flash Professional CC crashes when saving, corrupting files

    My company upgraded from flash CS5 to Flash Professional CC just recently, and i was hoping for a more stable experience, as Crashes when saving from Flash CS5 happened allmost daily. Seem i was wrong, occasionally when saving Flash CC crashes, and ends up breaking my work files... I ususally manage hundreds of files during a week, so having a stable enviroment is quite important for me. Any suggestions? Other than getting rid of Flash, though this is fast moving up the list...

    Yes, I allways have the most recent version.
    Guess i just have to work locally again, as i was forced to when using Flash CS5. Its frustrating, as some of the files (non-flash) i produce is  edited by other colleagues on the server. And i need to sync those files back  to my computer, to keep everything up to date... Not to mention i have  to sync the files i produce to two different servers. A project consist of at least 40-80 flash files and each of them accompanied by several files... xml, images, sound, and so on...

  • Adobe bridge crashes when saving illustrator files

    Hi there,
    We are developing custom connector using Adobe Drive SDK for our DAM system, the integration with CS was working fine, we recently updated Adobe Drive to 4.2, and we are encountering bridge crashes when saving illustrator file. It didn't happen with older version(4.0.2) of Adobe Drive, not sure why. I pin point the part that causing the issue: in our custom connector, we have READ_XMP_METADATA capability which we need to display the thumbnails and previews, and in the ftp sample connector, this capablity is not included originally, so the issue does not happen, but if I add this capabilty, the crash issue happens as well. If we exclude this capablity from our connector, this crash issue doesn't happen.
    We noticed this only happens when saving illustrator file, not photoshop or indesign, and it seems that only in illustrator, when save, and the bridge has the current file folder showing, we are seeing there are twice folder refreshes, and usually it will crash after the second time. In photoshop and indesign, we don't see folder refreshes. If switch to other folder, the crash won't happen. We tested on both windows and Mac, on Mac, this seems happen less often. Another thing we noticed is in debug mode, or we have many debug logging turned on, the crash happens less often, if it is deployed with no debug logging, the crash happens almost everytime. So we are guessing it might be some synchronization problem. 
    Could you please advice what's the cause of this issue?
    Thanks,
    Katherine

    Has it ever worked?
    What kind of files are they and where do you save them?
    Is a printer connected, set up and turned ON?
    Have you already tried resetting the preferences?
    Generally it's not a good idea to just save old files, because then some artwork may be automatically flattened. Illustrator will save the file to the old version file-format and if you used new features in-between, those cannot stay live in the old version file format.

  • Photoshop crashes when saving for web and devices

    When hitting saving for web and devices, Photoshop starts to render images but before it's done, it crashes. I get an error-popup with no text and the screen where normally the animation is shown is red. Then Windows comes with a crash report and I can only quit Photoshop.
    I have an animation of over 150 frames, but just some black and white lines, no color.
    I'm using Photoshop CS 5.5 on Win7.
    I tried deleting the preferences in AppData/Roaming etc, but no result, still crashes.
    My Photoshop is also updated to the latest version.
    Help?

    Ok, here's a crash report from Windows (not sure which I should post so just gonna post them both..)
    Naam van toepassing met fout: Photoshop.exe, versie: 12.1.0.0, tijdstempel: 0x4d90cf71
    Naam van module met fout: Save for Web.8BE, versie: 12.0.0.1, tijdstempel: 0x4d90d758
    Uitzonderingscode: 0xc0000005
    Foutoffset: 0x002d2e96
    Id van proces met fout: 0x1f4c
    Starttijd van toepassing met fout: 0x01cdb1fca2dd8dcb
    Pad naar toepassing met fout: C:\Program Files\Adobe\Adobe Photoshop CS5.1\Photoshop.exe
    Pad naar module met fout: C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Import-Export\Save for Web.8BE
    Rapport-id: fa9784f8-1def-11e2-a242-00238bb26d31
    Photoshop.exe
    12.1.0.0
    4d90cf71
    Save for Web.8BE
    12.0.0.1
    4d90d758
    c0000005
    002d2e96
    1f4c
    01cdb1fca2dd8dcb
    C:\Program Files\Adobe\Adobe Photoshop CS5.1\Photoshop.exe
    C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Import-Export\Save for Web.8BE
    fa9784f8-1def-11e2-a242-00238bb26d31
    Where can I find a Photoshop Crash Report?

  • Illustrator CC crashes when saving to network drive

    Hi all,
    We have 3 Macs all running 10.10 or 10.9 which crash when saving eps file types (PDF saves fine) to a NetApp network drive using Illustrator CC 2014.1.0 release.
    Users can save files locally and then copy the files to the network drive with no problems.
    Anyone else having this issue?
    Thanks in advance
    Colin

    Colin,
    It is always recommended here to open/save from/to own hard disk, and to copy from/to networks and removable media. You may be lucky, at least for a while, but it is better to be safe than sorry.
    In addition to the (far greater) risk of file corruption, some issues are mentioned here:
    http://helpx.adobe.com/illustrator/kb/illustrator-support-networks-removable-media.html

  • InDesign CC crashes when saving as .idml

    InDesign CC 9.2 x64  crashes when saving  as .idml. I have triied reinstalling but the problem persists.

    Adobe tech support "uncorrupted" the indd file I sent them (a file from
    Adobe's Classroom in a Book series) then they saved it as an idml file.
    Problem solved -- at least for that file. Thank you. It's still not clear
    to me, however, whether this was an isolated incident or something more
    systemic. I guess I'll find out the next time I try to save an indd file in
    the idml format.

  • Photoshop Crashing when saving.. causes?

    Recently both copies of Photoshop I use 8.0 and 9.0 CS has started crashing when I save a document. This is random and seems to do it one day and is fine the next. It started about two weeks ago, I did all the usual repair prefs etc, used Onyx etc and the problem seemed to go - today it's doing it again, this time I have run all the repairs etc but it has not solved the problem. No other progs are affected. It's only happening on my work G5 iMac.
    Any ideas?

    Apps such as graphic converter, appleworks, msn, virex all crash when trying to save something. msn crashes when changing my display picture, or sending a file to anyone. but the other ones just crash when i save. i noticed it with appleworks first, as i created a photo. so i just took a screen shot of it. but then converting the file to JPEG via graphic converter when clicking save, it crashes and says unexpectically quit! i finally got the picture to save by using preview. so i got the picture as a jpeg but now i cant send it on msn or set it as my display picture as it also crashes. i did a virus scan, then saved it but it CRASHED. i have only noticed it with these applications, im hoping that it doent effect imovie HD, as i use it a lot. Can anyone help me. i think this problem could be from a recent update.
    eMac G4 800mhz   Mac OS X (10.4.6)   Own iMac G3 600mhz
    eMac G4 800mhz   Mac OS X (10.4.6)   Own iMac G3 600mhz

  • Labview crashes when creating large image files

    I have a problem with Labview 6.0.2( I've tested evaluation version 7.0 too).
    I'm constructing a very large image, for example: 4500x4500 pixels. Labview crashes when converting the pixture to a pixmap. The image is fully constructed on my screen (in a picture control), but when converting it to a pixmap (for saving the image in a known format (bmp, jpg, tiff)), Labview crashes.
    I did some testing and when the number of pixels exceeded the limit of 2^24(16777216), the file 'image.cpp' crashes on line 1570. The vi to convert it to a pixmap is: P'icture to pixmap.vi'
    Does someone know a workaround for this problem? Or is there a fix for it?
    Thank you!

    I've tested the 6i version of my VI in Labview 7.0 evalutation version. It raised an error but not the same error:
    d:\lvworm\src\lvsource\compatexport.cpp(37) : DAbort: Called a routine not in the compatibility LVRT table
    $Id: //labview/branches/Wormhole/dev/lvsource/compatexport.cpp#11 $
    0x004BD4CB - LabVIEW_Eval + 0
    0x0EB710D9 - lvs248 + 0
    0x094C87A0 - + 0
    So i replaced the picture VI's with the 7.0 evalutation version VI's, and it worked. It is now possible for me to construct very large image files!
    I see no attached VI to test. But i guess it is also solved in Labview 7.0
    I used this file to convert the picture to image data:
    C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib
    \picture\pictutil.llb\Picture to Pixmap.vi
    And this file to convert image data to bmp:
    C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib\picture\bmp.llb\Write BMP File.vi
    I guess i have to write a workaround for this problem:
    divide the picture in blocks of 4096 x 4096 and then merge the image data arrays of the bloks together.

  • Applications crashing when saving

    Apps such as graphic converter, appleworks, msn, virex, all microsoft office applications and itunes all crash when trying to save something. msn crashes when changing my display picture, or sending a file to anyone. but the other ones just crash when i save. i noticed it with appleworks first, as i created a photo. so i just took a screen shot of it. but then converting the file to JPEG via graphic converter when clicking save, it crashes and says unexpectically quit! i finally got the picture to save by using preview. so i got the picture as a jpeg but now i cant send it on msn or set it as my display picture as it also crashes. i did a virus scan, then saved it but it CRASHED. iTunes crashes when exporting library information. i have only noticed it with these applications, im hoping that it doent effect imovie HD, as i use it a lot. Can anyone help me. i think this problem could be from a recent update. i also did a disk utility and it says the volume MacintoshHD needs to be repaired. should i backup my HD and re-install or is there a easier way?

    Hi Julian,
    Yes, you should always have a backup, so backup now.
    i also did a disk utility and it says the volume MacintoshHD needs to be repaired.Did you run "Repair Disk" from your install disk or another volume and it could not repair after several passes, or did you "Verify Disk" from your OS X volume? If you have not run repair disk you should do that:
    Steps for using Disk Utility
    1. Insert your Mac OS X CD-ROM disc or Restore DVD disc, then restart the computer while holding the C key until you see the spinning gear..
    2. Once started up from CD or DVD, choose Disk Utility from the Installer menu.
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from disc to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume, if necessary.
    6. Click Repair.
    If you repair errors run it until no errors found.
    -mj
    [email protected]

Maybe you are looking for