8.2 DSC : Program Crash After 24 Hours on 'Read Traces.vi'

Hello,
I am chasing a problem in a LabVIEW 8.2 project. The project uses DSC and on a trending screen, I use the 'read traces' VI to read traces from the Citadel database to display on trends.
After about 24 hours of running, the program crashes with "Error 1025". The dialog box reads: "Error 1025 occurred at Tag \\My computer\UPP Tags\Hy-6022_Actual: Open VI Reference in CTL_hdProxyManager.vi->HIST_ReadNumericTraceCORE.vi->HIST_ReadNumericTraces.vi:2->ReadTraces(Numeric).vi:1->!Dash Reactor.vi"
Under "Possible Reason(s):" there is a lot of text, starting with "LabVIEW: Application Reference is Invalid"
I don't seem to be reading an inappropriately large amount of data (in the last occurrence of the error, there were only about 750 data points per trace displayed on the graph, representing about 1 hour of data. The program is running with no operator interaction during this time. The application is updating the graph and therefore running the "read traces" VI about once every 4 seconds. I have 175 shared variables. The PC is a very new, fast one . Let me know what other data you might need.
I attached the main VI (there are a lot of support VI's too, but at least you can see the general idea), along with BMPs of the location of the error on the block digram and the error dialog box.
Michael
Michael Hampson
President
XL Automation, Inc.
Attachments:
ReadTracesError1.zip ‏195 KB
!Dash Reactor.vi ‏1837 KB

Hi Michael,
This was reported to R&D (# 4258E9IQ) and was fixed in LabVIEW 8.2.1. Upgrading to that version should fix the problem you are facing.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Similar Messages

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 ?

Firefox automatically crashes after 4 hours of use and only when a textbox is being used - problem now daily and getting worse

This has been going on for a few weeks and started of it's own accord. I have not recently installed any new plugins or scripts, and my PC is protected by two antivirus products and so my system (WinXP) is malware free.
I can browse firefox for up to 4 hours, and then it crashes. No matter what sites I am using, what I am doing or even if I'm at the PC... so long as there's a text box on the page then firefox will crash if the 4 hour time limit expires. I can be just about to save an hours worth of photo captions and lose all that work due to the crash, or can be in the middle of a background download but it'll still crash... daily.
I thought this was a plugin issue, as I have disabled all plugins for javascript handling, flashgot, etc, but still it crashes. (previously on startup Firefox would hang for 5 to 10 minutes and the system would "bing" at me if I tried to click on the firefox window... eventually a 'non responsive script' window would appear relating to a flashgot script). The crash used to go whereby suddenly the page would freeze for a few seconds, followed by a minute or two of safe working, then 2 minutes of freeze and 30 seconds of safe working, with the ratio of freeze-tim:working time working in 20 seconds increments until firefox crashed... now though there is no warning, the page freezes and then it's gone. I have updated firefox several times and still the problem persists. On a previous computer, Firefox degraded to the point where it froze for 4 minutes on any page with a Flash application... now on this computer it has degraded by itself to the point where it crashes after 4 hours of use.
I'm presently using Internet Explorer to type this question because firefox crashed again and I'm not going to sit waiting for it to reload just to get a few numbers from an information screen... therefore further info like crash ID's etc will be update in due time....

Cool, I'll try using the wall adaptor just as soon as I get a convertor for it to convert it to our socket type. It's nice to hear that someone else has experienced the same issue.
I am not using it as a phone in Australia, just the ipod and wifi.

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

My computer is crashed after 3 hours, when am running an Executable file from LabView 6.0.2

My VI is using DAQ6025e and GPIB cards, it is countiniusly writing data to files and talking with 2 GPIB instruments and one Serial instrument. Sudenly after 3 hours of perfect working it is crash my computer.
Does any body know why ??? Help? S.O.S?

Some questions to help us troubleshoot:
1)How crashed is your computer when it crashes?
Blue Screen Of Death crashed? If you don't know about BSOD then that
is when your computer presents a blue screen (white in XP) and tells
you that the system is halted, gives you a register dump and the
memory address where it stopped (all of which is useless unless you
are an assembly language wizard) and then you have to reboot the
machine.
Application error that kills LabVIEW.exe? Usually a pop-up MSGBOX
style dialog box will appear with a such and such error occurred in
LabVIEW.exe or another application and an OK button.
VI Slows to a crawl w/hourglass in the app window? Program doesn't
stop executing, it just stops responding to user inputs.
LabVIEW error cluster error that causes the VI to quit?
2) What O/S are you running? Win 3.1, Win 95, Win 98, Win NT 3.1, Win
NT 3.5, Win NT 4.0, Win2000, WinME, WinXPHome, Win XPPro?, Linux?, Mac
O/S?
In the Microsoft family, WinNT and Win2000 are by far the most stable
and reliable of the various versions of Windows with Win95 and Win98
having a lot of problems running for long periods of time. Make sure
that you get WinNT 4.0 updated to service pack 6 if you are still
using 4.0 but haven't updated the service pack level yet. There were
quite a number of problems with it when it first came out that have
since been cured.
3) Have you run the LabVIEW VI profiler yet? This will point out
memory leaks that are due to dynamically built arrays using shift
registers etc. or appending to strings, or improper IMAQ management,
etc.
4) Have you brought up the task manager and looked at the memory
allocated for LabVIEW.exe and for the whole system as well? Is it
growing? Sometimes there can be memory leaks that don't show in the
profiler that will show in the task manager when you look. These can
be due to bugs in LabVIEW itself or some driver for some hardware you
are using, etc.
If you are not running NT or a later derivative, then you won't have
task manager available but you can get diagnostic tools that are very
similar to task manager from off the web.
5) How much memory do you have in your PC? How fast is your PC? What
does the CPU % usage look like under task manager when you first start
your app? If it is running >40% CPU usage for any significant amount
of time at the start then perhaps your PC is overloaded with work and
you need a faster PC or your code needs redesigning. I like data
acquisition systems to operate <25% generally speaking. This number
seems to improve the reliability of the code that is running on them.
6) How much H/D space is available? You say you are writing data to
files. Your h/d space isn't running out is it?
7) Is it possible to run one instrument at a time for several hours to
see if it is a particular instrument that is causing the crash? Make
sure that your GPIB cards are properly configured so that they don't
share resources with any other devices(IRQ, DMA, memory addresses,
etc.) It may be possible that they behave fine most of the time even
with shared resources but if they ever try to send a command
simultaneously and they share resources, they could "collide" and
crash your PC. You can check all this out in the control panel and/or
MAX.
8) Is it possible that your serial port is getting hung up after
running a long period of time? Serial port UARTS are notoriously
finicky especially over longer line lengths and higher data rates. It
could be that your serial instrument is locking up your app or your PC
serial port is locking up your app and causing the crash. Can you put
a serial port analyzer in between your serial instrument and your PC
to see what's going on when it crashes?
9) Are you trying to read or write to the serial port in more than one
thread or while loop or dynamically launched vi? If you are you MUST
protect the serial port access with a semaphore or a VISA resource
lock. You CANNOT use a boolean global to protect access. Regular
globals aren't atomic and you can have race conditions that result in
unintended serial port collisions between differen threads. I have
seen this lock up multi-threaded serial programs before to the point
of requiring rebooting.
This problem can be especially frustrating if you haven't done
multi-threaded before. The port won't necessarily lock up right away
or at the same time every time. You MUST make sure that serial port
access is limited to ONLY ONE execution thread at a time.
10) Is there another application or service running in the background
with your application that may be trying to access the serial port or
GPIB cards when you aren't expecting it? This could cause a collision
that could crash your system as well.
Douglas De Clue
LabVIEW developer
[email protected]
Yan wrote in message news:<[email protected]>...
> My VI is using DAQ6025e and GPIB cards, it is countiniusly writing
> data to files and talking with 2 GPIB instruments and one Serial
> instrument. Sudenly after 3 hours of perfect working it is crash my
> computer.
> Does any body know why ??? Help? S.O.S?

All programs crashing after re-installing OS X

Hi all,
I've recently made the jump over to Mac form Windows and invested in a new 17' Macbook Pro. Sadly today someone decided to play a little trick on me and convinced me to run the Sudo FM command in Terminal and I lost my OS.
After re-installing OS X i'm now having problems with my programs. I've reinstalled the Apps disc but every program i Launch seems to crash after a few seconds (i'm yet to find a program that doesn't crash).
I have a time machine that has backups, but i presume that's not saving any program data, just my personal files, so i guess thats not going to help. Can anyone suggest how I can get around this?
Many thanks.

How did you reinstall? I'm guessing that something wasn't done properly... maybe you installed on top of remnants of the old OS (IIRC, even "sudo rm" can't remove files that are in use) and something is screwed up because of that.
Time Machine certainly is capable of backing up the entire hard drive, including system files, apps, etc., and does so by default. If you have an up-to-date Time Machine backup, and you hadn't excluded anything from the backup, you can restore from that. To do that, see item #14 on the [Time Machine FAQ|http://discussions.apple.com/thread.jspa?threadID=1964018].

Program shutdown after ~12 hours

On a PXI system running a 6071 DAQ at 50K samples/s on 16 channels, W2000 shuts the LabVIEW app off. Sometimes it shuts everything else off too, and the OS crashes. Sometimes the OS stays alive enough to ask for a reboot. Sometimes a few items remain on the screen, but mouse and keyboard are dead.
Attachments:
STM_THA_test_2.vi ‏125 KB
errors.txt ‏243 KB

I think Lynn was correct in suspecting a memory issue.
I will venture a guess that after 12 hours you getting the trigger you are looking for.
After the trigger the history is read and formatted for file.
Now it is time to math.
After 12 hours of 50,000 samples/sec on 16 channels you have alot of data.
I wipped a quick test VI to help figure out how much memory is being used.
You are collecting 800,000 samples/second.
Formatted as text, the string length is 4G (that is for one second).
For 12 hours you need 2.1 tera bytes of memory to buffer the string!
So....
I would suggest that you truncate the data to a couple of seconds prior to the trigger event and save the data as binary.
Do post processing to convert it to text
latter.
I hope this helps,
Ben
Demo attached
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
Memory_Abuse.vi ‏39 KB
Memory_Abuse.JPG ‏12 KB

Program crashes after 10 seconds

Hi when i start final cut pro X i can see all the normal screens, but after +- 10 seconds, the program crashes.
It is the trial version, ans i have already reinstall my OSX mountain lion 10.8.4
It doesn't help
liefst in het nederlands aub, en anders ga ik mijn beste engels moeten boven halen
greets mario

You need to give detailed information about your computer. You can also try the usual delete preferences http://www.digitalrebellion.com/prefman/

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.

Program crash after editing individual tracks

When I'm recording a multitrack music project in Soundtrack Pro, I often double-click an individual track to work on it as a stereo file. Lately, almost without exception, after I've worked on an individual track, and save it, the program crashes. The error message says: "An Unexpected Problem . . . CNSExceptionWrapper type 16777216 . . . could not parse the file URL 'file://localhost/Volumes/RAID/TemporaryItems/folders.501/TemporaryItems/..."
I've tried resetting the locations for Temporary Items to the Soundtrack Pro Temporary Items folder on my hard drive, which has plenty of free space. But I'm still having the problem...suggestions?

Utilizing all the cores and all the memory is not what you are after. You have to leave resources for other processes and you have to make sure that your system has enough resources to do things like decode footage in the background and process the effects you are setting up in AE. Some video codecs do not respond well to MP rendering so you may have to turn that off or transcode your footage to something that works.
As Myenium said your question lacked the details necessary to even guess what is going wrong. The best option to troubleshoot your problem is to reset your preferences to the default settings then see if the project works. If it doesn't start exploring things like source footage formats for problems. Then start adjusting your memory and MP settings using the guidelines that Adobe has published for optimizing performance.

AI CS6 Crashing after an hour or so...

Illustrator CS6 is crashing after about an hour or so of work every time I use it every day. If I forget to save, I'm screwed. Is there a crash log I can provide to an Adobe rep that can help decipher the problem? It was happening on another computer too with plenty of horsepower. I was hoping perhaps it was just a bug that with the most recent updates from Adobe, it would be fixed. Not the case. Still crashing after an working for an hour or so...extremely frustrating.

Plenty of horse power. Well maybe but how do we know this? One users horse power is another uses brake!
If you rpovide us twih information on the processor, the platform, the type of font management software, kinds of fonts you have, the size of your scratch disks, the amount of free space, the amoung of RAM (some users think 8 GB of RAM is like WOW state of the art, its not) then what kind of plug ins, other software you run and what types of utlities you general have running.
With more info someone might be able to help you.
I personally suspect you are either running out of space on your srcatch or you might be working with a corrupt font.
Of course your preferences could be corrupt and your permissions might be hampering you from access part of your scratch.

My compiled program crashes after first run (LabVIEW 2009)

I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly.
The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM). On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's. Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running. The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down. The program is then gone from memory as far as I can tell. There are no processes in memory or anything.
Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once.
In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see. Also, when I run my program in the development environment the program does not behave this way. It has no problems at all.
I have used this style of architecture before in LV8.6 with out any problems. Can anyone suggest some possible solutions or even some debugging tips? I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue.
Thanks for any help.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!
Solved!
Go to Solution.

I have solved the problem I think (at least as far as testing to this point has revealed). After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher. My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI. My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories. What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down. This is my supposition about what may be happening any way. I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running. This fixed the problem, or at least worked around it. If someone out there can explain to me exactly what is happening I sure would appreciate it.
Thanks for all the help those of you who responded. Your advice was very beneficial and certainly led me to a resolution faster.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

Most programs crash after latest update..

I just ran Software Update. It had all of the iApps, Quicktime, and the latest Security Update in it.
Then I rebooted. Next I installed the latest Xcode.
Once that finished I proceeded to run my regular apps, Mail, Adium, etc.
Mail starts, but after some amount of time (10 or 20 seconds) crashes displaying crash reporter.
Adium will run until you double-click a contact to open a message window.
So, not much else will run. Camino's fine, Opera seems Ok. But Safari crashes after a few seconds. I even went and manually downloaded the latest Security Update installer, and even it crashes!
Disk Utility seems to work fine, thankfully. I ran Verify Disk (it's Ok) and Repair Permissions (it fixed a couple of minor directory permissions) and I'm still SOL.
I'm an ex Windows guy, had the Mini just about a year now - so I'm pretty clueless on what to do next. Any help much appreciated!!!
Thanks,
Steve

hi steve
at this point since this is a system wide issue you may want to consider archiving and installing your operating system. http://docs.info.apple.com/article.html?artnum=107120. this helps in a lot of cases like this. remember to repair disk beforehand, and do software updates. however, do not do the last update which created the problem. may get everything back to normal. good luck.

Programs crashing after security update 2014-002

I installed the latest security update for Mavericks today and since then I've had two programs crash repeatedly.
In iTunes, when I click on "Add to Library," iTunes shuts down.
In Photoshop Elements 12, when I try to save a photo, the program shuts down.
Has anyone else had similar problems? I can't think of anything else that would be causing this, as it hasn't happened before.
Note: I have a late 2013 Macbook Pro with Retina.

Bump. I'm having a similar issue.
Since installing the latest Mavericks security update, my Retina MacBook Pro (13-inch, Late 2013) has crashed and restarted a minimum of once per day for no apparent reason.

Programs crash after 10.4.9/10.4.10 update...

I have an Intel MacPro 2.66GHz machine with 2 gigs of ram. Since installing the 10.4.9 update (and also skipping over 10.4.9 and installing the 10.4.10 combo updater)...
1. QuarkXPress 6 and 7 crash when I trying to pull down the "Window" menu.
2. Entourage 2004 crashes when composing an email and I try to select a font from the font popup menu in the new email composition window.
3. Photoshop CS2 crashes on startup.
4. FlightCheck 6 crashes on startup.
5. AdiumX (chat program) crashes when I try to access the "Status" menu either in the menubar or in the buddy list window.
Temporarily disabling a majority of the fonts installed have allowed some of the above problems to go away. However #1, #2, and #5 still occur. EVERYTHING was running just fine prior to the 10.4.9 update.
I have tried reinstalling said apps, repairing permissions, running disk diagnotic apps like DiskWarrior, removing font caches files with FontNuke, removing program preference files/folders, and these problems are still happening. Can someone clue me in as to what has happened?
BTW, these same problems have also occurred on a totally separate Intel machine. I also have several PowerPC machines that are comparably configured that were updated to 10.4.9/10.4.10 and are NOT exhibiting the above problems.

Hi Carolyn,
I found the answer. Several months before installing to the 10.4.9/10.4.10 updates, I had removed the AquaKanaRegular and AquaKanaBold fonts from the /System/Library/Fonts folder. This because old information I had said these two fonts were not necessary.
However, on page 74 of the November 2007 Macworld magazine, the article shows that those two fonts are indeed necessary.
Once I restored those two fonts to their rightful place, my apps have stopped crashing. Yayyy.
Thanks,
Jon

8.2 DSC : Program Crash After 24 Hours on 'Read Traces.vi'

Similar Messages

Maybe you are looking for