Assigning memory on windows os crashing labview app

Hi
I must be doing something really stupid and very easily crashing my pc by writing only few functions in labview!
I want to pre-allocate memory of 5GB at the start of application. So I used simple initialize function to create 2d array of NaN dB points as shown in the image. I have 8GB of memory but the error popped up as shown in screen. And I only tried 1GB as shown in image. Could I not have this pre-allocation?

k-waris wrote:
Hi
I must be doing something really stupid and very easily crashing my pc by writing only few functions in labview!
I want to pre-allocate memory of 5GB at the start of application. So I used simple initialize function to create 2d array of NaN dB points as shown in the image. I have 8GB of memory but the error popped up as shown in screen. And I only tried 1GB as shown in image. Could I not have this pre-allocation?
Are you running LabVIEW 32-bit? You can't allocate that much memory with a 32-bit operating system or in LabVIEW 32-bit.

Similar Messages

IPhone causes Windows to crash immediately when Camera app is on...

I sync my iPhone with two computers: an iMac for music, videos & photos, and my Dell Inspiron D860 running Windows XP for my work e-mail, contacts, and calendar.
If I have taken a photo with the iPhone and either leave my iPhone in Camera mode, or have even left any photos in the "Camera Roll" album in the Photos app, then my Windows PC crashes immediately when I hook the camera up for a sync. As soon as the USB cable makes a connection, I get an instant blue screen: informing me of a BIOS memory error and a message saying that Windows is shutting down to prevent further damage. So, I disconnect the iPhone and reboot the computer.
However, if I delete any images in the Camera Roll album of Photos and make sure that the iPhone is not running Camera when I plug it in, I can sync between the iPhone and iTunes on Windows XP flawlessly.
The irony here is that I have left the sync Photos box unchecked in iTunes on the Dell running XP. So, technically, nothing in the Camera or Photos apps on my iPhone should even be communicating with software on the XP system.
Have other folks experienced this problem? If not, perhaps I'm doing something wrong and would appreciate any insights!!
Thanks

I finally nailed it.
i have a Acer Aspire notebook with orbicam and i had the latest driver from ACER but still had some problems on XP but deleted everything (Orbicam drivers and camera utility from Control Panel) also i verified that everything was gone in MY PC / Properties / Hardware / Device Manager / Imaging Devices (if not, uninstall the Orbicam from there.
then i restarted my computer and installed Logitech Quickcam utility version 10.5 from logitech site (from the Quickcam 4000) that i previously downloaded, everything went ok.. i restarted again my computer and my camera worked perfecty and also i was able to connect my iphone with photos in camera roll and XP detected it normally without any trouble. The only thing that came out after doing this is that my Orbicam appears in the SAFE DEVICE REMOVAL UTILITY right next to the other utility icons and the clock. i will try to solve this and post any coments.
I hope this info is useful for others like me with this issue.

How to stop Windows phone 8.1 app from crashing?

Hi All,
I have developed an app in Windows Phone 8.1 environment (WinRT). When i tested the app in my local testing device, it worked fine but when i hosted the app on app store, it sometimes crashes. Please help me, how do i stop my app from crashing?

Sometimes crashes or always crashes when deployed through the store?
If you want to rely on data instead of magic then check the crash reports as Abdul suggests. If you want magic then my crystal ball says that if it always crashes the app is trying to write to its install directory.
The install directory is writable for test deployed apps but not for apps deployed from the store.

My iphone 5s will not sync with itunes windows, it crashes as it is trying to sync the apps. Thoughts?

My iphone 5s will not sync with itunes windows, it crashes as it is trying to sync the apps. Thoughts?

How is your iTunes "spacebar" looks like?

Bug: Windows 7 DLL call to turn off monitor message crashes LabVIEW 10.0f2

Hi,
I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 286873
I was trying to find a way to turn off a laptop lcd
monitor during measurements. I was trying to replicate this
http://codereflect.com/2009/04/03/how-to-programmatically-turn-onoff-your-monitor/
which uses windows messaging.
I found the attached Monitor-1.vi somewhere on the forum that seems to do the above.
However when I run the VI it crashes LabVIEW 10.f2 on Windows 7 32-bit.
cheers
David
Solved!
Go to Solution.
Attachments:
Monitor-1.vi ‏13 KB

Hi Cosmin,
That was it! Thank you so much!
I will let NI UK support that you identified the issue and get them to close the CAR.
cheers
David
Attachments:
Turn off Monitor.vi ‏12 KB

GetDefaultPrinters (WinAPI call) Crashes Labview

Hi all,
For several reasons I need to use the windows API to get the default printer. I know about labview's activex solutions but those are not universal.
See attached VI. This winapi call crashes labview rather consistently. It runs fine and returns correctly the default printer. However, some time later, a few seconds or a few operations later it will always crash labview. Why? I've tried changing it to "Run in UI thread" instead of any thread but neither seems to help...
To get it to crash immediately, try closing the VI. That seems to do it every time. Access violations...
Solved!
Go to Solution.
Attachments:
defaultprinters.vi ‏10 KB

No. You actually did NOT allocated memory in your VI.
Here is how to allocated memory, the old way:
George Zou
http://webspace.webring.com/people/og/gtoolbox

Windows 8 crash

I wrote a VI for controlling 3 New-Era syringe pumps and a Eurotherm 3216 temperature controller.
The 3 syringe pumps are piggy backed one after the other, and the first syringe as well as the temperature controller are connected via USB-to-Serial to a YOGA2PRO idea-pad running a 64bit Windows 8.1 running Labview 2013
My problem is that the program causes windows to crash, resulting in the blue reboot screen with the error "Multiple_IRP_complete_requests"
This error occurs at different stages of the programs and can occur after 10 mineuts or after an hour of running.
When I transfer the exact same VI to a 32bit Windows XP Lenovo running Labview2012 the program runs without a glitch!
I tried rewriting the VI to account for communication collisions or timing issues but havent been able to solve this mystry!
For now Im running my program on the "old" computer, but I would greatly appreciate any help or suggestions on the matter.

Here are all the files.
In addition, I removed all the unnecessary stuff from the code.
I have no reason to believe the crash occurs due to anything but the labview, because there is absolutly nothing else on the computer besides the OS.
and this error keeps hapening only when I run the program
Thanks again.
Attachments:
Controller and Syringe pump.vi ‏35 KB
Eurotherm 32xx Series.zip ‏1045 KB
NE-50X.zip ‏1012 KB

Windows 7 crash from iphone 6 plus sync with itunes 12.1.1.4

The sync starts and then windows 7 will crash to the blue screen, dump the memory, and try to restart. So far, I have not found a solution to this issue. Please help. (windows 7 crash from iphone 6 plus sync with itunes 12.1.1.4)

Greetings strepac,
Welcome to the Apple Support Communities!
I understand that iTunes is becoming unresponsive when you connect your iPhone and try to sync it. In this situation, I would recommend reading over the attached article and working through the suggested troubleshooting steps within.
iTunes: May become unresponsive when connecting iPhone, iPad, or iPod touch - Apple Support
Cheers,
Joe

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

Labview app wont run on fresh reboot unless MAX is started.

I am a Labview NOOB. I am the only IT here and started about a year ago and basically got thrown into the "labview" with 0 labview experience.I had to take an xp machine and turn it into a win 7 machine.
Here's some specs: labview 8.2 32bit running on windows 7 32 bit with IO libraries 16. Driving a gpip to usb 34970A data aquisition unit and a temperature compensation oven. Heres the situation. When i restart the PC my "temp_comp.exe"(application that labview consultant wrote) will not run. I get a few errors One as soon as i start the app: "oven Communication Fault" and one when i try to run the oven with shortened testing times and temp:
error 107387202 occurred at visa close in HP34970A close.vi-
34970A_read.vi>measure oven temp.vi->wait for oven to reach temp vi-
a comp loop.vi - a test loop sequence.vi>main temp comp.vi
Possible reasons VISA: hex 0xbfff009e a code library required by VISA could not be located or loaded.
I have reformatted a machine with xp and was able to get this running fine.
So here's the kicker. If i open up MAX and expand the devices and interfaces tree the program works fine and dandy. no errors. I have ran 3 batches in the oven over night with no problems. I figured i would just do an easy work around and have the max program start during startup but i have to manually expand the devices and interfaces tree before it will work.
Any ideas will be super helpfull Cheers!
Solved!
Go to Solution.

It never ceases to amaze me what managers think is possible. It would be difficult for even an experienced LabVIEW programmer to port a LabVIEW app from XP to Windows 7 using a version of LabVIEW not supported on the operating system. Tell them you'll see them in a few months.
I ran into an issue once where a vendor's Win7 dll had different default settings than the priginal and we couldn't figure out why we couldn't communicate with the I/O card. Seems that they inverted the address bits as default. Of course, there was no documantation on the change - unless you count the source code itself.
It was an intentional change which would make sense if you were someone who bought a new card and never used the old dll before. But guess what? The card was already obsolte/unsupported, so there AREN'T GOING TO BE ANY NEW USERS!
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.

Cluster wired to UDP Write Crashed LabVIEW

In the Windows version of LabVIEW 6.0, I am allowed to wire a cluster's output directly to the Data In of a UDP Write node. However, when it is executed, LabVIEW crashes. The Linux version 6.1 doesn't allow that connection. Is this a change between 6.0 and 6.1 or a bug in the Windows version?

No, it never behaved correctly. I am very inexperienced with LabVIEW. I was practicing building a front panel on a Windows 2000 machine with 6.0 eval. I wired the UDP Write as I described and tried to run it. Each time I clicked the button that activated the UDP "code", LabVIEW crashed. I copied the .VI to our Linux box with LabVIEW 6.1 Full Version and, when I brought it up, the line between the cluster and the UDP Write was dashed. I then changed the diagram so that all of the items in the cluster were converted to U8 using byte-swapping and word-splitting, converted it to a binary array, converted that to a string and sent the string to the UDP Write and cured the problem. I wanted the inputs into the cluster to have the exact data structure as defi
ned in the C header for readability.

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)

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

NI-Fieldpoint support in Windows 7 and LabView 8.6

We have a "classic" FieldPoint system with an ethernet controller. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Window 7. Is NI-FieldPoint supported in LabView 8.6 and Windows 7?
Regards,
nate
Solved!
Go to Solution.

Hi natewkidd,
I feel like there is some confusion between the operating systems running on a development machine (like Windows 7) and the real-time operating systems that run on our real-time controllers (like the FP-2000). I will do my best to clear up this confusion by first answering your questions.
1) What is the difference between LabView Real-Time 2009 and LabView 2009?
LabVIEW Real-Time 2009 is actually a software package officially known as the LabVIEW 2009 Real-Time Module that is installed after the LabVIEW 2009 development software to allow the user to develop and deploy real-time applications to real-time targets such as your FP-2000. You can think of the LabVIEW 2009 Real-Time Module almost as a plug-in for LabVIEW 2009 to allow for real-time application development and deployment.
2) If I have a FP-2000 on the ethernet network and want to use a computer running Windows 7 and LabView 2009 to record and display data, will I still be able to communicate with the FieldPoint network using the FieldPoint Read/Write VIs from my Windows 7 machine?
If you were just going to use the FP-2000 as a network module (NOT deploying a real-time application to run on the FP-2000 itself), you should be able to communicate with it using just the FieldPoint Read/Write VIs from your Windows 7 machine with LabVIEW 2009 and the NI-FieldPoint 6.0.5 driver. In this situation, you actually do not need the Real-Time Module since you are not deploying the application to the real-time target.
Regarding the FP-2000 not being supported beyond LabVIEW 8.5.1, this is because the memory on the controller is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Real-Time Module and the LabVIEW 2009 Real-Time Module. For more information on this please check out this KnowledgeBase article.
I hope this is helpful! Let me know if you have any further questions.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Assigning memory on windows os crashing labview app

Similar Messages

Maybe you are looking for