Labview logging program crash windows after 2 days

I am using Labview 8.0, and running the executable the program. What this program does is that it acquires data and then writes to hard drive. Each set of data is small but it writes also every second. It will create a new file every day so the file does not get too big.
After 2~3 days running, it crash windows. I think it somehow used up all the resource so the windows would not even response any more. And we need to run this program continually for at least one month.
So is this a memory leak problem of the executable program generated by Labview app builder? or could that be Labview does not release memory after it writes data to the file, and eventually used up the resource?
any suggestions?
Thanks

It is on a laptop with win xp, 1GB Ram. each data is only 40~50 bytes. The concatenate strings does not duplicate in memory, right? what about build path and open file? Do I need to close the file inside the loop? It is a very small program so I attached a screen capture here.
I am going to let it restart again and check memory usage tomorrow.
Thanks,
Attachments:
screen shot.gif ‏36 KB

Similar Messages

Cannot log in to Windows after restoring image

After an apparent successful restore of an image to a Gateway M250C laptop the Novell Client log in box appears. The Advanced option only shows a Windows tab. When a log in to Windows is attempted it appears it is going to work then the Novell Client log in screen reappears. This is only happening with the Gateway model above. I have several to image and it's happening with all of them. Images for other Gateway models, IBM desktops and laptops, and Lenovo desktops and laptops work fine. The current version of Novell Client is 4.91.5.20100928. I've reinstalled it on the original computer and recreated the image with the same result.
Any ideas?

btippett,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Why does my data logging program slow down after a while?

A data logging program created with Labview 5.1. Slows down after a few weeks and creates files in the Temp. directory.Computer is Siemens Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also using Solartron Dig. probes and Fieldpoint units.

Any chance that you are using Win 95/88/ME? Those OS's have well documented
memory leaks which will consume all your available memory if an application
is run long enough. Also there are some issues of memory management within
LabView in the allocation of memory.
The solution to the first is to switch to WinNT/2K. The second will be much
more difficult.
On Thu, 22 Feb 2001 03:19:12 -0800 (PST), Freek wrote:
>A data logging program created with Labview 5.1. Slows down after a
>few weeks and creates files in the Temp. directory.Computer is Siemens
>Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also
>using Solartron Dig. probes and Fieldpoint units.
===========================================================================
SolidW
orks Research Partner National Instruments Alliance Member
Christopher Dubea Phone: (504) 847-2280
Vice President of Engineering Fax: (504) 847-2282
Moving Parts L.L.C. email: [email protected]
P. O. Box 6117 URL: http://www.movingpart.com
Slidell, LA 70469-6117

How can I diagnose a Labview RT program crash on cRIO 9073?

I have 2 cRIO 9073 purchased about 1 year apart. Both are running the same realtime application. The first cRIO runs fine. The 2nd cRIO crashes intermittently while executing 1 particular VI that contains 2 timed loops running in parallel (1 collecting data and the other controlling machine movement). When it crashes, the app stops, web server and FTP stop responding, MAX cannot communicate with the device ( I must perform a hard reset). After reset, viewing the error log using MAX shows no errors. I've added message logging to see if it stops in a particular place, but see no patterns. In some cases, the device seems to be continually restarting (every 2-3 minutes) until it finally hangs. In many instances, my configurations files (used to store runtime variables) have been corrupted or erased. When trying to deploy the app on this Rio, I generally must try multiple times because I receive the error, "Error deploying on target". I have tried formatting the flash and reinstalling the OS many times from different sources.
I'm running Labview 2009, SP1 with the FPGA option.
Any ideas on how to diagnose this problem? Are there any diagnostic tools to test this device?

Here's a better description of what I'm trying to do. This system is used to control the head position on a test machine. I used the LV RT wizard to create the base VI with 1 deterministic loop and 1 non-deterministic. The deterministic loop schedules 2 different test. Test 1 is every 5 minutes (collect analog data, read temperatures, calculate new head position based on temperature , drive stepper motors to new position, collect data after moving, then dismiss). Test 2 runs once a day with a duration of about 4.5 hours (drive stepper motors to user defined position, simulatiously collect data at various rates from 5Hz to .01 Hz, drive head to next user defined position, etc). This test has 2 timed loops running at different rates, one collects data, the other moves the head and acts as a timer to know when to move to the next position.
If I never run test 2, then the system has never crashed, leading me to believe the problem is in the test 2 VI. The crashes don't necessarly occur in the Test 2 VI. On some occations 1-2 hours after Test 2 has completed, the CRIO will start rebooting itself (every 2-3 minutes). This may happen 4-5 times until it will finally hang completely.
Since the crashes happen randomly (it may run for 2-3 days before crashing) I'm trying to find some way of trapping errors or exceptions that would give me some clue as to what the problem may be.

Options to log program crashes/errors for deployed apps

I've done a bunch of reading on the topic and am getting mixed information. In my case, I have a released application running on four Win7 targets. Ocassionally, I'm getting some application crashes. I am certain there is some firmware-level problems going on with my custom IO board as well, but I need some tools to troubleshoot why the CVI app is crashing.
I've seen recommenation to try the Windows Event Viewer, Dr. Watson (for WinXP targets), etc, but these are pretty generic.
This is a good thread, but didn't go anywhere.
And then there's the article on the ConfigCVILogging tool. This seems promising too, but it's unclear to me how I can package that EXE with my app distribution. Also, what setup do I need in my app so that it is aware of the CVILogging EXE?
Ideas?

Hi Electrolund,
It would be helpful if you could post screenshots of any errors you are seeing when these crashes happen. Could you describe how the applications crash exaclty? Does it always happen after a certain input or action or is it pretty much random? Does it happen in the same way on all 4 test computers? I think you are a little confused about the way that ConfigCVILogging tool works. I believe the way it works is that any time the run time engine DLLs are called that application will know about it and make entries to the log. So running your executable should visible to that process.
Regards,
Basil
Applications Engineering
National Instruments

All apps and programs crashing even after restore

Hi, after my ipad completely died, all apps and programs now crash about 15-20 seconds after opening them. I have tried everything to correct this:
- uninstalling/reinstalling apps (even though this happens to the default apps as well, such as Settings and the App Store
- Cleared temp files/cookies
- Turned off Spotlight Search
- Closed down any open apps (do this all the time anyways to save batt life)
- Soft reset the device
- Completely restored the device
Nothing has worked and the closest Apple store is 3 hours away. I would prefer some other solutions other than being directed to the store if at all possible
Some other side notes:
- I have the original ipad 1
- I am on iOS 5.0.1
Thanks!!

Well here I am again after having to do this two more times, and guess what? Apps are closing out again...it only took a matter of hours for it to start happening again this time. There has got to be a better way to fix this...would a repair shop be able to figure out what the problem is? this is the only apple product i've ever owned and unfortunately, their lack of support and my experiences are not giving me the warm fuzzies...

Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1. The code was saved with the 'Save for Previous Version' option available in Labview 8. When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes). Are there any ideas what's going on and how to fix this?
Thanks for your help!
Mike

I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
Try to take over the world!

All programs crash after Time Machine restore

After noticing that Photoshop hung the system every time I tried to open it, I ran a disk utility scan on my system disk. It came back that my hard drive was bad. I purchased a new hard disk, installed it into my Mac Pro, booted from my Snow Leopard CD, and tried to restore from my Time Machine backup to the new hard disk.
After restoring, my system boots but every program crashes shortly after I open it. If I open Dashboard it crashes after a few seconds... Mail... crashes after a few seconds. All of these programs worked fine on my "bad" hard drive. The only apparent problem was that attempting to open Photoshop would hang the system.
My original hard drive that was backed up to Time Machine was 300 GB. My new hard drive that I'm attempting to restore to is 2 TB. Does this matter?
Any ideas on how to get a stable system restored?

Ack226 wrote:
It came back that my hard drive was bad. I purchased a new hard disk, installed it into my Mac Pro, booted from my Snow Leopard CD, and tried to restore from my Time Machine backup to the new hard disk.
How did you format the new drive?
How did you do the restore? Did you do a full system restore, starting with your Snow Leopard Install disc? If not, what?
Have you done a +*Verify Disk+* and +*Repair Permissions+* on your internal HD, via Disk Utility?
It's possible that as your disk was failing, it corrupted things on your system, and Time Machine backed those changes up, so the restore brought them back. If everything else checks out, you might want to try the restore again, but select an earlier backup.

InDesign CC crashes always after quit

InDesign CC crashes alway after quit. Every time I quit InDesign CC I get the error message that the program crashed. After restarting InDesign CC I have to do all the presettings again. What can I do?

Thanks PrintFusion4s,
I have not installed the fonts:
Ithornët
Typo3-Medium.ttf
Typo3Normal.ttf
batang.ttf
Savoye LET
BUT i fixed the problem, want share to all users for ref.
Step 1) I backup all of fonts from "user library font folder" ((not the system library)) to desktop new folder
Step 2) Open Font books and delete all user fonts.
Step 3) Then I put back the backup fonts by "A fonts.... > B fonst.... > C fonts.... "into the "user library font folder"
Step 4) "A" fonts put there, then try to open Indd, no problem, "B" fonts... no problem... "C" fonts...
Step 5) I found 2 bad fonts:
MHeiGB-Bold.ttf
MHeiGB-Medium.ttf
Then All fonts is no problem.
BUT the step 2) is a MUST, because I have 2 macbook pro, when the 2nd times I only delete MHeiGB-Bold.ttf, MHeiGB-Medium.ttf, the indd CC still quit. After I try step 2) then put all others fonts into "user library font folder". The indd CC is work.
My english is poor, hope it can help all~
Thanks share~!!

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

Long running VI crashes about 30 days by Windows 7 bluescreen

Hi Everyone,
My background is as an Electrical Engineer with some programming experience, LV, C, VB etc, but nothing approaching a computer science type level of understanding.
I have a test system that contains two hardware cards, the PCI-6033E for analog input to read a thermocouple and the PCI-DIO-96 to toggle a cooling fan when a set temperature threshold is reached. There are up to 36 test stations that this program runs. Each station individually isn't complicated, but there are 36 of them.
The original VI has been around for quite some time. It was running on Windows XP and needed to be run on a Windows 7 PC. The VI was first written to use the traditional DAQ interface methods. For the drivers for the hardware to work on Windows 7 they needed to be upgraded to NI-DAQmx drivers. That meant a bit of recoding to implement the new style.
The VI and computers would run under XP for weeks on end without any trouble. The PC's nor VI was not routinely restarted. When the new version was placed on the Windows 7 PC's the VI would run for a period of time around 30 days and then a windows error box would pop up.
There are three of these same systems running this same hardware and same VI. Two of them had this error occur after 28 days and another was a few days after that.
Thinking that this could be a memory leak issue, the systems have been restarted and have been running while monitoring memory usage and there does not appear to be an increase in memory consumption over about a week's time.
I have attached the Desktop Execution Traces to this post also. I didn't see any perpetually increasing memory buffer sizes or anything. Though I do wonder what the trace means by the Handle: Entry, is that the memory location being addressed?
Also, being that this error takes about one month to occur, running repeated stress-test (noting if the duration between errors goes up or down with increases or decreases in program load) type of iterations is impractical.
Questions:
1) Does anyone know of any driver issues regarding the support of relatively old hardware with windows 7?
2) When using the Desktop Execution Trace toolkit I see Memory Allocate events, but no memory release events. Should I be expecting some type of release event to be logged?
3) What does the Handle: address mean in the trace log?
4) As mentioned above my expertise is more in the electronics and hardware arena rather than the details of memory management and Windows PC architecture. It seems to me a driver issues would likely cause an error to be thrown from windows itself rather than LabVIEW as is the case here. If there were a memory leak would that error come from LabVIEW or Windows?
5) To you, what does this evidence point to as being the problem? Bad driver, poor VI programming, other Windows 7 conflict?
6) Any advice in further tracking down this problem?
Thanks,
Brandon
Attachments:
11_17_2011 _ 16_18_22_582723.txt ‏3251 KB

Andrey -
In some cases Windows able to show in which *.sys driver an error occurred. This info should be also somewhere in saved minidump.
And also check Windows Event Logs - probably something happened shortly before Blue Screen.
That's kind of the problem. I looked at the "help" that was offered by windows at the time a bit, but I couldn't make any sense out of all the information that was there. There was a really long .xml file that unfortunately was mostly compuspeak to me. Some names and words were recognizable, but I couldn't get context so I didn't learn anything from it.
About the code itself. It is definitely not optimized in any shape or form. It appears to be hacked together by a lab engineer without much more than basic training in LabView. Kudos for them getting it to work when it was constructed, however now there is a problem. Unfortunately there wasn't time (budget) for a rewrite and cleanup so a quick swap of hardware related code was all that was done.
Did you ever run your new code on the XP machines?
Oddly, no. Not for any length of time. A simple functional verification was all that was done with the new code on XP. A long term run on XP will be done in the coming months.
We will need to know What version of LabVIEW as well as the DAQmx version. A simple screenshot from MAX>> Software would suffice. Is this occurring with a VI running in the IDE or a deployed executable?
The VI is running from an installer compiled from Labview 2010.
The MAX Screenshot:
Attaching your code would allow us to look for places the code could be optimized such as re-opening DAQmx Tasks or arrays built in loops (It Looks like you've got a few on a quad core machine and the compiler is loop expanding from the instances where a buffer keeps upping size by 4)
The trace has a number of memory resizes that increase the memory allocated by 8, up to a certain level, something like 804 or some number. This would occur many times and always stop incrementing at that same number 804 (or whatever it actually was). There would be a different handle for each of these sequences. The fact that it does not keep incrementing towards infinity makes me think this is not a big issue. In the trace log it is lines 1473 through 1572 and 1632 through 1731 for instance. That section of code is here:
Thank you all for being helpful on this one. I appreciate the time you have taken to offer advice and solutions. The top level VI is HILT36A.vi.
Attachments:
Win7 HILT_36A.llb ‏876 KB

Various programs crash after upgrade to 10.6.4

Various programs crash after upgrade to 10.6.4 but only late in the day / evening. There seem to be no crashes early in the day.
After a reboot the problem is fixed and things seem to work OK.
Might this be some kind of memory-related issues?? Programs not releasing memory until eventually there's nothing left?
I'm a Windows guy until recently so am not up to speed with Mac software / hardware yet.
Any suggestions?
Thanks.

Hi, I am facing major instability in MS Office for Mac 2008 after the 10.6.4 upgrade. Programs (Word, Excel, PowerPoint), just crash randomly. Mostly when opening existing Office documents but there is no fixed pattern.
Tried Office auto update but no joy.
Any suggestions
Here is the MS Error log
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXCBADACCESS
Date/Time: 2010-07-23 20:37:36 +0530
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.2.5.100505
Crashed Module Name: libTrueTypeScaler.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x00009bd5
Blame Module Name: libTrueTypeScaler.dylib
Blame Module Version: unknown
Blame Module Offset: 0x00009bd5
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Operating System Information
Operating System: Mac OS X 10.6.4 (Build 10F569)
CPU: Intel Core Duo, Number: 2, Speed: 2147 MHz
gestaltPhysicalRAMSize err = 0, result = 2047 MB
gestaltSystemVersion err = 0, result = 0x1064
Screen: 1440 x 900, depth = 32, ltbr = 0, 0, 900, 1440
Microsoft Application Information:
Error Reporting UUID: 0B338D65-7DAA-4B4A-B8B1-0C17F587C24A
Time from launch: 0 hours, 14 minutes, 46 seconds
Total errors on this client: 40
Does this help at all ?

Setup program crashes when you try to install a 2007 Office on a 64-bit version of Windows 7

Hello there,
I have a Dell Vostro machine with Windows 7 Pro 64-bit installed on it. It came with Office 2010 preinstalled on it. About 6 months ago I removed Office 2010 and installed Office 2007 with no problems. Yesterday a user messed up her office so badly
that I had to uninstalled it in an attempt to reinstall to ensure that all missing files exist. A few seconds after selecting my options, the installation program crashes. I tried it with a few different users logged in to make sure it's something related
to the profile of the user I was logged in as.
Just to be clear, this is the same Office 2007 installation that was installed correctly on it about 6 months ago and the same product key.
Why is this happening and how can I fix this issue without having to restore the computer to its default state?
Any help is appreciated.
Thank you,

Hi,
Please refer to this kb, use Microsoft Fix it 50154 to uninstall Office 2007 completely:
http://support.microsoft.com/kb/928218/en-us
Then try installing again.
We can also perform a clean boot to install, which gets rid of the background program conflicts:
http://support.microsoft.com/kb/929135
Hope this can help.
Regards,
Melon Chen
TechNet Community Support

Adobe illustrator crashes right after I Close the tutroial window!! Help!

Adobe illustrator crashes right after I close the tutroial window!! Help!
I just purchased illustrator after my trial period. It wont run! And have resinstalled several times. Cleared my font cache. cleaned my registry. Tried logging as a diffferent user.
Im on windows 7
I need this to work now!! I have a deadline for a project and this damn program wont work now. WTF Adobe. I'm screwed.!!
Help me please now asap!

This can be caused by a permissions problem with AI being unable to write the Preferences file to the proper folder. You can try running the program as an administrator.

Windows 8 apps crash immediately after opening

Windows 8 apps crash immediately after opening
when ever i open any app downloaded from windows store some of them crashes immediately.......
after re-installing it only works for 1-2 days then again same problem

Hi,
Please also check these two blogs to see if any suggestion work for you when the issue happens again:
Fix Store App in Windows 8.1
http://blogs.msdn.com/b/notime/archive/2013/10/18/fix-store-app-in-windows-8-1.aspx
What to do if your Windows 8 Modern App fails to start
http://blogs.technet.com/b/askperf/archive/2013/10/11/what-to-do-if-your-windows-8-modern-app-fails-to-start.aspx
If the issue still persists, please post back the %TEMP%\winstore.log
and saved AppModel-Runtime and Apps event logs under Event Viewer>Applications and Services Logs>Microsoft>Windows here for our research.
Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
Kate Li
TechNet Community Support

Labview logging program crash windows after 2 days

Similar Messages

Maybe you are looking for