LabVIEW 8.5 Bug Report: VIExecState.cpp, Line 530

This bug seems to restricted to the attached code. Any change to the VI block diagram which in turn marks the VI changed
in the title bar with an asterisk. If I try to run the VI in its
unsaved state it crashes with the VIExecState.cpp Line 530 error.
This is how I induce the fault using the attached code.
1. Before starting LabVIEW add "DWarnDialog = TRUE" to the LabVIEW.ini file without the quotes.
2. Open "BurnIn Shelf 2 - Shell Only.vi"
3. Click the "Run" toolbar icon code then click "Abort Execution".
4. Edit the block diagram e.g. add a free label.
5. Click the "Run" toolbar icon again.
6. This should induce the VIExecState.cpp, Line 530 error.
As this is a "warning" I have set "DWarnDialog = TRUE" in the LabVIEW.ini before starting labview. This means any warnings not critical to execution are displayed immediately. They are normally kept hidden until you start labview. Unfortunately, things like occurence notification stop working so its critical to some of my code implementations. Remove this entry from your labview.ini if you have finished debugging.
I have not found the source of the issue in my code yet. The error has been reported to NI UK. CAR reference for this error is #45703. I will keep the forum informed of any developments.
David
Message Edited by David Crawford on 04-07-2008 04:19 PM
Attachments:
BurnIn Shelf 2 - Shell Only Folder.zip ‏893 KB
lvlog04-07-08-15-53-15.txt ‏4 KB

Hi David,
Thanks for posting this on the forums so that the community can be aware of the issue, I believe you spoke to a collegue of mine yesterday and in turn he has filed the Corrective Action Request for R&D to look into.
All the best,
Applications Engineer

Similar Messages

Labview version 6.1 failure:"linker.cpp", line 2302

I have the labview version 6.1 failure:"linker.cpp", line 2302 fault.
Does any one can help me please ?
Solved!
Go to Solution.

Actually HeapPeak existed as far back as LabVIEW 4 or maybe even 3. However it is not usually helpful for linker errors as that is something in the LabVIEW compiler itself. HeapPeak can be sort of useful for Insane errors to locate the element that the compiler considers insane (and consequently delete and/or rewire it).
If this is a recent error on a VI that used to work before, it is most likely related to a corruption to the VI and the best course of action is to replace the VI from a backup (source code revision control would be a great advantage here). If it is something where no previous (working) state is known about, then it is going to be a tough cookie. This version is 14 years old and eventhough I still have some installation of that version somewhere it is several years ago that I started that up for more than some accidential reasons. I'm pretty sure NI would need to do some archeological work nowadays to come up with a system they could use to replicate such an error and the OP would need to be a pretty high profile customer that they would go through that sort of effort.
Maybe it is related to this error. It is the closest available in the publically accessible list of errors. A complete recompile of the entire source code tree is definitely one of the first actions to try. It may fix the problem or run into even more errors that could maybe point into a more specific location. Upgrading to a more recent LabVIEW version is another possibility although hampererd by the fact that the currently shipping version isn't officially supporting XP anymore and that the Vision software is one piece of software that underwent serious changes in the course of time and an update from 6.1 to the most recent version is most likely not a seamless operation.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Internal Software Error: .\Vobulator\MuxPlanner\AudioPackPlanner.cpp, Line 530

I am trying to make a movie and burn it to a disk for school but I keep getting that error (Internal Software Error: .\Vobulator\MuxPlanner\AudioPackPlanner.cpp, Line 530) It occures after about 5 or 10 minutes of transcoding. The original file was a mkv file format with a dts audio and a avs video track.
Here is the detail of the video.
Format                           : Matroska
Format version                   : Version 2
File size                        : 6.56 GiB
Duration                         : 2h 10mn
Overall bit rate                 : 7 197 Kbps
Encoded date                     : UTC 2011-10-26 03:46:55
Writing application              : mkvmerge v4.8.0 ('I Got The...') built on May 24 2011 03:12:58
Writing library                  : libebml v1.2.0 + libmatroska v1.1.0
Video
ID                               : 1
Format                           : AVC
Format/Info                      : Advanced Video Codec
Format profile                   : [email protected]
Format settings, CABAC           : Yes
Format settings, ReFrames        : 5 frames
Muxing mode                      : Header stripping
Codec ID                         : V_MPEG4/ISO/AVC
Duration                         : 2h 10mn
Bit rate                         : 5 689 Kbps
Width                            : 1 280 pixels
Height                           : 528 pixels
Display aspect ratio             : 2.40:1
Frame rate                       : 23.976 fps
Color space                      : YUV
Chroma subsampling               : 4:2:0
Bit depth                        : 8 bits
Scan type                        : Progressive
Bits/(Pixel*Frame)               : 0.351
Stream size                      : 5.05 GiB (77%)
Writing library                  : x264 core 119 r2106 07efeb4
Encoding settings                : cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=12 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=5689 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Language                         : English
Audio
ID                               : 2
Format                           : DTS
Format/Info                      : Digital Theater Systems
Muxing mode                      : Header stripping
Codec ID                         : A_DTS
Duration                         : 2h 10mn
Bit rate mode                    : Constant
Bit rate                         : 1 510 Kbps
Channel(s)                       : 6 channels
Channel positions                : Front: L C R, Side: L R, LFE
Sampling rate                    : 48.0 KHz
Bit depth                        : 24 bits
Compression mode                 : Lossy
Stream size                      : 1.38 GiB (21%)
Language                         : English
Knowing that Encore does not support mkv I demuxed the mkv taking out the video track into a .h264 file using mkvextract. I then muxed it into a mp4 without the audio using mp4box then dragged it into encore without any problems. For the audio, I just demuxed it out into a dts and dragged that in as well. I then created a new timeline and dragged each peice of media into there corresponding sections on the time line. I tried to play the video but there was no audio. I treid to import the dts and got a warning saying something like, "DTS is supported in this version of Encore (CS5) but just not in preview. When I burn it to the disk there will be no problems" So I just went ahead and tried to build the video into a dvd folder for a dual layer disk.
The setting I have for the DVD is default except I changed the bitrate to 9.4mbps. That's the only thing I changed. (I used NTSC)
I played the audio using an external player to see if it plays and it did. When I check to see if there is any problems with the build it only says something about start remote and end action. I have never set them before so I don't think that should matter.
I have Encore installed on my secondary drive (Not C: which is windows) and I treid to create the DVD Folder on that drive. When I got this problem I just thought it was that it could not create the files on the drive because the program isn't running off that drive which it should be, I treid to create the DVD Folder on the C: drive and I still revieve the same error.
Does anyone know how I can get past this? I need this to be done by tomorrow for school in the morning.

Hi Stan and thank you for your concern, I was (I am) getting that in a timeline. and also a kind of general error when I was trying to build ether a folder or an image. I had made a copie of the project for me to delete all menus I also change all "end actions" who were on "stop" configuration but still my problem was there. In this project in encore two things I did witch may be the coz ot the problem?
-first when changing the menu styls and edition with Ps (maybe I did some thing wrong there?) and
-second when changing throught encore the markers on my principal time line witch maybe a did in a wrong way.
whatsoever thank you and sorry that I took a long time to answer, regarding my english writting you allready undertand that it is not my language. In addition I'm not a professional in editing but I'm still learning. I think it will be quiker for me to do the project again till the start on encore even if for me it wood be good for to know where the problem came from for me not to do it again.
Thanks a lot best regard
Fabian

Failure: "might.cpp" line 815 on LabVIEW executable

Hi,
I have a program written in LabVIEW 6.1 on a Windows XP platform. The program includes an ActiveX container that shows an Internet Explorer content window (just like the "Using the Microsoft Web Browser ActiveX Control" example found on http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9BF111EE034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p_answer=&p_source=External
, but without the activex queue in that example).
After I built the executable, I was able to run the exectuable on the development machine without problem. However when my client runs it on his PC with LabVIEW runtime engine 6.1 installed, he gets the message:
Failure: "might.cpp" line 815
For assistance in reso
lving this problem, please record the procedeing information and navigate to www.ni.com/failure or contact national insturments.
I cannot find any information on might.cpp on the NI support site. Any idea of what can be done to fix this problem?
Thanks!
Dan

Hi dan,
you must contact NI support sending them the problem. "might.cpp" is a source module of LV and they can investigate the error.
Another thing you have to take into account is that LV stores the class ID and not the application. Has the client PC the same MS IE version installed? If not, the error could also result from different versions of the Active-X control.
As with the reporting Toolkit for MS Office you have to build a different version of your app for each different version of the control.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Nickled and dimed once again by obscure errors. This is LabVIEW 10.0.1 on Redhat EL 5.5 32-bit.
I removed an enum from the project that is also used in a typedef control cluster. Since many VIs use this typedef I have to go to each VI and save in order to remove the phantom dependencies (i.e. popup can't find enum ctl when opening VIs). In the process of opening every VI and saving LabVIew is crashing on me reliably but not everytime just after I press cancel when it tries to find the enum ctl.
Here are the errors. Sometimes the address is null....I believe LabVIEW src code should check for null/bad pointers but does not in this case.
GenNAryOp_ArrayBase : naryop, setdef? ninp=1
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xFF
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x21
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt bool, csrc=0x30
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xA
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x50
LabVIEW caught fatal signal
10.0.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0xffffffff
Upon reopening LV I see this.
The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Hello wbdoyle,
I'm sorry you are seeing that error. Did you close and save the type def that included the enum? This should prevent you from having to go through and save each VI that includes the type def. Are you using the System Exec VI? Also, are you performing any data acquisition with the VI you are referencing? The error you are seeing indicates that the LV compiler isn't handling something in your VI and I want to pinpoint exactly what is happening.
Thanks!
Regards,
Anna L
Applications Engineer
National Instruments

Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

Dear colleagues,
Here is a bug report.
Culprit: 'Open URL in default browser.vi'.
System: Windows 8, Professional. LabVIEW 2011 SP1.
Abnormal behaviour and steps to reproduce:
Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode.
Looking forward to see this fixed.
Best regards,
Igor Titov.
CLD.
=========================
Igor Titov, CLA
WebPager - put LabVIEW front panels into the web page
Labicom.net

Hi Igor,
Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Fatal Internal Error source/manager/thread.cpp line 3472 while starting LabVIEW

When I try to begin LabVIEW 7.1.1 on my mac OS X 10.4, I see the LV logo and then I get the pop-up window:
LabVIEW.app Alert
Fatal Internal Error: "source/manager/thread.cpp", line 3472
LabVIEW version 7.1.1
You will lose any unsaved work. For assistance in resolving this
problem, please relaunch LabVIEW, or contact National Instruments.
When I click on Continue, it kills LabVIEW. I also get 2 other
windows...one says Investigate Previous Internal Error...which does not
do anything, irrespective of what I click in that window.
The other window is called Controls.
The last message I see on the LabVIEW splash screen is Server: Exported VIs list ok.
The LV website says I need to make DLLs re-entrant, but I can't even begin LV to solve this problem.
Any suggestions?

Hi Enduro,
I would suggest creating a service request for this problem at ni.com/ask. The Applications Engineer will be interested in looking at the error log that is being created, so that we can determine if this problem has occurred before.
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments

How do I file Bug Report? Labview FPGA

I'm not sure if this is a software bug or what, but I'm trying to run the Analog Input example project for Labview FPGA , in "Find Examples >> Hardware Input and Output >> R Series >> Basic IO >> Analog Input - R Series".
The thing is, it works.. mostly.. I manage to send in a sine wave, and see it. However, every now and then, when I set teh Waveform Graph X-axis to autoscale, and change the Update Mode, every time I put it into mode Scope Chart, it freezes my computer, and I have to physically power off my computer and power it back up (which i'm not happy about). I'm using the default settings for the example, my card is in RSE mode, input signal at 25 Hz, 4V p-p
I doubt anyone can guess why this is happening, but is there any way to file a bug report?
Thanks,
Hardware: Quad-core Xeon 2.33 Ghz, 8 GB RAM, PXI-7583R FPGA, PXI-1036 Chassis
Software: Labview 8.6.1, LAbview FPGA 8.6., Vista 64-bit
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5

1... Adding an unrelated question to a 3-month old post is not the best way to get your questions answered.
Start your own thread next time.
2... The example works fine for me. The EQUALS function works just fine for strings. Be aware of some things, though:
Case matters. If you want to ignore case, then uppercase both strings (or lowercase them) before comparing.
Length matters "X" is not the same as "X ". "123" is not the same as "1234".
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

LabVIEW Real-Time and Remote Front Panel MemoryManager.cpp line 437 error

Hi all,
I'm using a smartcamera (NI 1742) with LabVIEW Real-Time 8.6.
When I look at the Front Panel with the web browser and I close the browser or I Stop the executable, I always get this error: MemoryManager.cpp line 437. I've checked if someone else had this error, but I guess I'm the only person who got this error. I saw someone who had the MemoryManager.cpp line 406, but mine isn't on this line.
The application works well, but when I got the error, I need to reboot the smartcam to get it works. In my application, I use the Modbus library and I read/write binary file in the hard disk of the smartcam....
Anyone knows the solution?
Thank you very much
Stephanie

Hi again,
Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI.
I really need help please!
Thank you
Stephanie
Attachments:
MemoryManager line 437 error.JPG ‏228 KB

Failure: scalesup.cpp line 767

Hi,
My vi is crashing and giving me the error message:
Failure: scalesup.cpp line 767
I have isolated the problem, and it occurs at a waveform graph property node. I have the property node set for Xscale.Markervals[ ] . I'm trying to create a set of custom markers by sending a 1D dbl array to the property node. This custom marker array is the same length as the data array (600 points).
Thanks for your help in advance.

Are you using a logrithmic scale? If so, then make sure that the value of one of the markers is not zero.
If not, then what version of LabVIEW are you running? Can you take your data and create a simple VI that das that data aas the default in an array and then plots it to a graph and then does the property node? This should be pretty easy to set up so that we can reproduce this issue.
Also, bug reports such as this one are normally handled better in an e-mail or phone support request.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Error #3: "memory.cpp", line 639; VI used to work, now it stopped

Hello,
I am running LabVIEW 6.0.2. I have a rather complicated VI that used to work just fine. I have run it a bunch of times without any problems. I have not changed anything at all, and now it gives me Error #3: "memory.cpp", line 639 every time I run it. Does anybody know what could have happened?
Thanks,
Corey

Corey,
Not without seeing the code.
Perhaps there is some memory leakage going on, or open references that cannot be resolved.
Also, check your memory to make sure it is still working (view your RAM amount).
Other possibilities include possible conflicts with software running in the background, or software you recently installed.
Check your task bar, and make sure your virus protection and anything else unecessary is off. These can eat memory and processor time.
Other than that, navigate to the site where the bug tells you to (don't remember off the top of my head) and report it to NI.
Good luck

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

LV 6.1, 3D Surface Graph sometimes collapses (doesn't work stably); plus blocks use of remotely controlled panel by LV run-time engine (error #26:"window.cpp", line 11518

1) "3D Surface Graph" does not work stably; sometimes it changes its properties (e.g. plot style) without me doing anything prior to that; a couple of times it lost a complete sense so that I had to delete the graph and install it again
2) I tried to remotely run a VI which contains a 3D Surface Graph in it. It turns out, the use of the "3D Surface Graph" somehow blocks the remote control over the panel. As a result of that, I got the following error message: Error #26: "window.cpp", line 11518 (with LabVIEW version 6.1).
3) Is it possible to plug into the 3D Surface Graph a few plots at
the same time since there is a built-in control "plot number" (somehow by bundling them up or putting into an array - I tried both but didn't work) or it can be done merely by use of 'case' structure preceding the Graph, where case structure decides which plot to pass into the 3D graph?
Attachments:
3D_Graph_ver_1.bmp ‏214 KB

Hello mjoler,
Thank you for contacting National Instruments.
The following example will show you how to plot multiple 3D plots on a single 3D graph. Modeling your VI after the example may also alleviate the instability that you have been experiencing.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B123AE0CBA19111EE034080020E74861&p_node=DZ52038
As far as the error you are receiving, it's difficult to say what could be causing this. ActiveX controls embedded on a front panel sometimes do not display on a remote client because they draw and operate almost completely independent of LabVIEW. If possible, try remotely controlling your VI with a client computer that has a complete installation of LabVIEW. The error could also be a bu
g. Try downloading the evaluation version of LabVIEW 7.0 from http://www.ni.com/labview. By doing this, we can determine if it is a bug in the older version that has been fixed in the latest version.
Let me know how this goes.
Matthew C
Applications Engineer
National Instruments

Lv crashes every 10 days, "plotsupp.cpp, line 1330"

This vi continually writes to a buffer and displays on a waveform chart. Upon a trigger signal, a predefined amount of data (in the buffer) is written to a file and the vi ends. Labview is crashing every 10 days with failure message "plotsupp.cpp, line 1330". Mac G-4, OS 9, LabVIEW 6.1, 6031 I/O Card, 38 channels of data.

Hello �
What happens every 10 days? Does the program get to the same specific point after 10 days of running? What does that specific part of the program do? Does the user have interaction with the VI or is it running by itself?
The only report of this error crash we have is when the user tried to modify the labels in a control. Somehow the control got corrupted and the problem was fixed by replacing the controls in the front panel with new ones.
If this does not help, you can narrow the problem down and post a simple VI so that we can reproduce the issue.
S Vences
Applications Engineer
National Instruments

Thread.cpp, line 1938

I got this error message when I was running my programm.
"thread.cpp", line 1938
labview version 6.1
I went to check "Task Manager", and it seemed like labview kept increasing memory its memory usage until there was not any left. so this error did not happen in the begining. It took some time.
Is this a bug of Labview6.1? Or where can I set up the maximum memory usage of this application so the computor won't be dead?
thank you.

This may be cause by a bug in your program. LV does automatic memory management for you, and it's usually pretty good about it, but if you use functions that require more memory during run-time, LV will allocate more and more memory until you run out. Good examples of this are Build Array and Concatenate String. If you use these in a loop to build a large array and do it fast, you may run out of memory pretty quickly.
Try using the profiling tools in Tools>>Advanced (I don't think they exist in the base package) to see if you can pinpoint the consumption to one of your VIs. You should also read the white paper about memory management in LV. You can find it in Help>>Search the LabVIEW Bookshelf or by searching this site.
If this is consistent and you can't solve it, I suggest you post your code.
Try to take over the world!

LabVIEW 8.5 Bug Report: VIExecState.cpp, Line 530

Similar Messages

Maybe you are looking for