Finding Memory Leak in LabVIEW

Hi NG,
we wrote a sort of hugh application in labview that collaborates with our
..NET driven
device framework and a variaty of unmanged c++ libs.
As we are now close to the release we did performance testing and it showed
up that
the app is consuming more memory continously.
We used prefomance counter to check whether the managed objects might not
get garbage collected
but this is done OK, since the handle count stays at a constant level.
We tried to figure out whether one of the c++ libs is causing the problem
but this is not the case either, since
the memory leak exists even if the lib functions are just not being called.
Even labview profiler is not detecting any inconvenient memory consumption
of any of our vis but
windows task manager notices a constant memory consumtion of the executable
(or of labview.exe itselve when running in
dev. environment).
Does anybody know what this might be? Has anybody a clue what other tools we
could use to figure out
where the problem is?
Any help is greatly appreciated.
Thanks in advance, Sebastian Dau!

"mfitzsimons" <[email protected]> wrote in message
news:[email protected]..
> Sebastian,
> Memory leaks can be VERY hard to find.  I use the divide and conquer
> technique that involves chunking (make into smaller code segments) your
> code into smaller pieces and running the smaller pieces until you find the
> memory leak.  It can take weeks to find the source.
you accelerate this process by using the labview profiler.
> The most common is arrays or any data that increases in size as the
> program runs.  To fix this you can use a FIFO that allows only so
> many elements to be added before deleting data out of the array.  The
> second source is opening references repeatedly and not closing them. 
> Look closely at any VI that open anything.  Do a search for "Memory
> Leak" on the discussion forum and you will find about 60 postings that may
> help. 
> Matt
> If you are using DAQ-MX <a
> href="http://digital.ni.com/public.nsf/allkb/BAF29EE03747EE4B86256E9700541436?OpenDocument"
> target="_blank">http://digital.ni.com/public.nsf/allkb/BAF29EE03747EE4B86256E9700541436?OpenDocument</a>
>  
>
arrays and refs have already been checked.
thanks, Sebastian

Similar Messages

Find memory leak

Hi All ,
In our SAP application server (Solaris 10 X86 running on hardware HP ProLiant BL685c G5) physical memory available is day to day decreasing drastically. We suspect, there is a memory leak.
Could you please let us know how to find memory leak in Solaris.
Regards,
Rajesh.

Hi Rajesh
Memory leaks have a large number of possible causes, including:
•Unsupported hardware or software
•Custom Scripting
•Misconfiguration
•Third party hardware and software issues
The prstat command can be used to gather basic performance data to help identify if there are any processes consuming a large amount of memory. For example, the data below is sorted by the SIZE column. SIZE is the total virtual memory size of the process:
prstat -s size
If you are experiencing some of the symptoms described above or if you suspect a memory leak, it is particularly important that performance data is captured so the memory leak can be confirmed. It is important to gather at least the following pieces of information:
•Process ID (PID)
•Size of the process
•The executing command
•The timestamp information showing exactly when the data was captured.
while true
do
for pid in `cat pids`
do var=`date|cut -d' ' -f4`
echo "$var :\c" >> ps.log.$pid
ps -eo pid,vsz,rss,pcpu,args | grep $pid |grep -v grep >> ps.log.$pid
done
sleep 30
done
You could check the memory utilisation details through
#mdb -k
::memstat
kmastatRegards
Sadiq

Finding Memory leaks in C using Visual Studio 2013

I am using Visual Studio 2013, and taking a course in C programming and we started
talking about memory bugs detaction, in particular memory leaks, and how to detect them using Valgrind on Linux.
I want to know if there is a way to detect such memory leaks using VS 2013. I tried searching online but it just leads to lots of articles and blogs and msdn posts and blogs with lots of words like dump files, and analyzing them, etc which is weird
because:
1) It sounds so complex, convoluted and unintuitive it is actually hard to comprehend it.
2) The main reason this is weird is due to the fact that VS is the most advanced IDE around and Microsoft spends so much money on in, yet from what I have read it seems that there is no simple way to use VS to detect memory leaks
- certainly no way that's as simple as Valgrind where I only have to compile the program and run the command valgrind -leaks-check=yes ProgramName
and it simply prints to me all location it thinks there is a memory leak and describes the error (like not freeing memory after allocating it with malloc hence having "dead" memory after the program finishes, or accessing memory that's out of
the array bounds)
So my question is how to use VS 2013 in order to achieve the same results and to find out First in high level if there are memory leaks in the program, and Second - to detect in a simple manner where those leaks are- preferably without involving dump files
(not that I know how to use them anyway in VS).

Hi MicrosoftLaw,
Thanks for your post.
Based on your issue, if you want to check if there are memory leaks in the C program from this VS2013. I suggest you could try to find Memory Leaks Using the CRT Library, for more information:
https://msdn.microsoft.com/en-us/library/x98tx3cf.aspx?f=255&MSPPError=-2147217396
In addition, I find a similar thread about this issue, please you refer the Dusty's suggestion to check this issue.
http://stackoverflow.com/questions/45627/how-do-you-detect-avoid-memory-leaks-in-your-unmanaged-code
I did some research about this issue, I found that the Visual Leak Detector extension tool is a free, robust, open-source memory leak detection system for Visual C++. So if possible, I suggest you could try to use the Visual Leak Detector extension
tool to find the memory leak for Visual C/ C++ program.
https://visualstudiogallery.msdn.microsoft.com/7c40a5d8-dd35-4019-a2af-cb1403f5939c
However, if you have any issue about how to use this Visual Leak Detector extension tool to find the memory leak for C program. I suggest you could directly to write a review to this REVIEW tab in Visual Leak Detector site.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Finding memory leaks in java

Hello,
I have a memory leak in my application. I have found other memory leaks in the software using JProfiler, but I have a problem with JProfiler finding this one. My biggest problem is the JProfiler itself. If I use short runs, the JProfiler works fine. If I run my application for more than half a day, the JProfiler eats up memory and after a while it stops responding.
I tried JProbe, but after profiling my application for 18 hours straight, it got buggy and wouldn't work correctly. It also ate up alot of memory, and couldn't process my snapshot after 18 hours of run. I saved all snapshots, and restarted JProbe. The initial snapshot was read correctly, but the final snapshot threw an NegativeArraySizeException.
So, now I am looking for other tools which are able to find memory leaks without hanging or crashing after running 24 hours. Any recommendations?

I dont know any other profiler you can use, but how about using the divide and conquer approach?
Disable a significant section of your application and let it run for a day. If the leak occurs, its in the non disabled part.
If it doesn't, its in the disabled part. Next, enable all the code. Then disable about half of the half that failed and try that. Continue doing so until
you isolate the code enough that you can look at it and hopefully find the problem. Note you will need to keep track of what you previously enabled and disabled as a test (I put comments in the code).
Alternately, you can look at functions that perform complex functionality that you suspect might be the problem and have the function return
dummy data rather than perform the functionality. If the leak goes away, its that function(s).
Example:
public String getComplexData(String arg1, String arg2){
//this section bypasses the complex code and returns dummy data
boolean x1= true;
if(x1==true)
return new String("some dummy data");
//complex functionality goes here.
Also of help would be to list everything that can cause a memory leak (I assume its a memory leak and not a resource leak such as not closing connections).
Here are some ideas:
1) persistant class variables that are a collection that have objects added to them but never deleted and allowed to be garbage collected
such as static class variables, session scope variables, or application scope variables.
2) An object tree where one of its nodes is never set to null to be garbage collected (such as a static class variable).
If you are running a web application in a clustered enviornment, try running it on only one server.

Looking for memory leak in labview 6.02

dear all,
my labview program needs an increasing amount of memory when running (at the time about 12k/s) which leads to swapping memory on my hdd.
i have found out that calling cluster references like Controls[] or decos[] leads to this kind of memory leak and made a work around for that (simply calling it only once at runtime) but there are more memory leak(s)which i cannot find. The bugs that i have found searching the labview resources does not answer my problem.
does anybody already found out more memory leak problems ?
thanks

I have been seeing similar behavior; I too have not found all the
leaks. I think I have slowed the allocation by replacing some of my
'build array' functions with the combination of 'initialize array'
followed by 'replace array subset'. The drawback to doing it this way
is that you have a fixed maximum number of elements allocated just once
rather than allowing an array to grow incrementally. Please let me know
if you try removing build arrays and if that helps.
By the way, there is a checkbox under the options menu to deallocate
memory as soon as possible - if you don't mind that your program runs
more slowly, this may help to avoid the problem, at least temporarily.
-vinny
ciossek wrote:
> dear all,
> my labview program needs an increasing amount of memo
ry when running
> (at the time about 12k/s) which leads to swapping memory on my hdd.
> i have found out that calling cluster references like Controls[] or
> decos[] leads to this kind of memory leak and made a work around for
> that (simply calling it only once at runtime) but there are more
> memory leak(s)which i cannot find. The bugs that i have found
> searching the labview resources does not answer my problem.
>
> does anybody already found out more memory leak problems ?
>
> thanks

Finding Memory Leak

Is it possible to find the memory leak using the following command
java -Xprof <classname>Regards
ackumar

Here is the output for one of my class. I didn't use any "java.net" class in my code.
But it shows java.net.SocketInputStream.socketRead() is interpreted 50.0%
I am in bit confusion . So plz help me.
Flat profile of 93.41 secs (4041 total ticks): main
Interpreted + native   Method
50.0%     0 + 2012    java.net.SocketInputStream.socketRead0
0.0%     0 +     1    java.lang.ClassLoader$NativeLibrary.load
0.0%     0 +     1    java.net.SocketOutputStream.socketWrite0
0.0%     0 +     1    java.lang.ClassLoader.defineClass0
0.0%     0 +     1    sun.misc.URLClassPath$7.getInputStream
0.0%     0 +     1    com.mysql.jdbc.SingleByteCharsetConverter.<clinit>
0.0%     0 +     1    com.mysql.jdbc.MysqlIO.checkErrorPacket
0.0%     0 +     1    com.mysql.jdbc.Connection.<init>
50.2%     0 + 2019    Total interpreted
     Compiled + native   Method
0.4%    15 +     0    cern.colt.matrix.impl.DenseDoubleMatrix2D.zMult
0.2%     7 +     0    java.lang.FloatingDecimal.readJavaFormatString
0.1%     4 +     0    com.mysql.jdbc.ResultSet.getString
0.1%     0 +     3    java.lang.String.<init>
0.1%     3 +     0    com.mysql.jdbc.SingleByteCharsetConverter.toString
0.0%     2 +     0    cern.colt.matrix.impl.DenseDoubleMatrix2D.getQuick
0.0%     2 +     0    com.mysql.jdbc.Buffer.readFieldLength
0.0%     0 +     2    java.io.BufferedInputStream.read1
0.0%     1 +     1    java.lang.FloatingDecimal.doubleValue
0.0%     2 +     0    java.lang.Integer.parseInt
0.0%     1 +     0    java.util.ArrayList.get
0.0%     1 +     0    java.util.HashMap.hash
0.0%     1 +     0    com.mysql.jdbc.MysqlIO.readFully
0.0%     1 +     0    com.mysql.jdbc.Connection.getCharsetConverter
0.0%     1 +     0    com.mysql.jdbc.ResultSet.getInt
0.0%     1 +     0    cern.colt.matrix.impl.DenseDoubleMatrix1D.assign
1.2%    42 +     6    Total compiled
         Stub + native   Method
48.3%     0 + 1943    java.net.SocketInputStream.socketRead0
48.3%     0 + 1943    Total stub
Thread-local ticks:
0.4%    18             Blocked (of total)
0.0%     2             Interpreter
0.3%    11             Compilation
Flat profile of 0.01 secs (1 total ticks): DestroyJavaVM
Thread-local ticks:
100.0%     1             Blocked (of total)
Global summary of 93.43 seconds:
100.0% 4127             Received ticks
2.1%    85             Received GC ticks
0.0%     2             Interpreter

Subpanel problem & memory leak in Labview 8.0

Hi,
I just installed Labview 8.0 Evaluation package yesterday. I tried to
code a user interface class using dqGOOP object oriented package. It
seems that LV 8 behaves differently from LV 7.1 which is good. One can
use same subvivi in multiple subpanels. I however run into problems
with this new feature i.e. I cannot edit the subvi after it has been
placed on two subpanels. Editing is possible after LV 8 restart.
In my code I create two similar object instances from the panel class. I have a class method panel_run which puts itself on the subpanel defined by refence. I have two subpanels on the main vi, one for each of my panel_run instances. I do not stop the panel_run instances cleanly, instead I use the Labview stop button to stop the execution. Once the main vi has runned, the panel_run subvi cannot be edited any more. When one opens the panel_run
subvi, a clone of the subvi is always opened instead. One cannot modify
the clone. After a few runs, I also got a memory segmentation fault
from labview, which then crashed. I was unable to repeat the crash.
I attached the code. Use panel_test.vi to start the program. Is
there any way to get around this problem of not being able to access a
subvi after it has been placed on a subpanel?
Regards,
Tomi
p.s. Sorry for the wrong category. This is Labview 8.0 problem. There
was not however a category for labview 8, so I selected Labview 7.1.
Tomi Maila
Attachments:
panel_test.zip ‏569 KB

Open your panel_run VI --> you get a clone
Press CTRL+M --> Will open your VI (Not the Clone)
Close the Clone and work on the VI.
PJM
Got EasyXML?
JKI.VIPM.EasyXML.OpenG.LAVA.Builder.blog

How can i detect "Memory leak" with large LabVIEW projects.

Hi,
I have a huge LabVIEW application that runs out of memory after running continuously for some time. I am not able to find out the VI that is hogging up memory. Is there any tool that dynamically detects the VI that is leaking memory.
Or, is there a tool or a way to identify the critical areas which can be potential culprits that is leaking memory.
Regards
Bharath

Bdev wrote:
Thanks Dennis.
I think Desktop Execution toolkit should solve the problem.
Wayne Wrote
Have you tried Tools»Profile»Performance and Memory ? http://zone.ni.com/reference/en-XX/help/371361F-01/lvdialog/profile/
But this will just give me the amount of memory used by the VIs and not the amount of memory that is not getting released.
And where is the problem about that? Just try to find what VIs keep increasing in memory size. That are the culprits. If you have real memory leaks, meaning there is memory that is not managed by LabVIEW directly but for instance by a DLL somewhere and that DLL looses references to memory, so it goes really lost, then the only way to find that is by successively exclude functionality in your application until you can find the culprit.
There is no other simple way to find out about who is loosing memory references than by doing debugging by exclusion until the problem disappears. The only way to speed this up, which quite often works for me is doing an educated guess, about what components are most likely to do this misbehaviour.
Not knowing anything about your application and if you are talking about memory hogs (fairly easily identifiable by the mentioned Performance and Memory monitor) or actual memory leaks, it is hard to tell how to go about it. Memory hogs are usually the first thing I suspect escpecially with software I inherit somehow from people from whom I'm not sure they know all the ins and outs of LabVIEW programming.
If a leak seems likely the first culprit usually are custom DLLs (yes even DLLs I have written myself), then NI DLLs such as DAQmx, etc. and last there come leaks in LabVIEW itself. This last category is very seldom but it has happened to me. However before going to scream about LabVIEW having a memory leak you really, really should make sure you have very intensivly researched all the other possibilities. The chance that you run into a memory leak in LabVIEW, while not impossible, is so small compared to the other ways of causing either a memory hog or running into a leak in an external component to LabVIEW, that in 99.9% of the cases where someone screams about a LabVIEW memory leak, he is simply wrong.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Active X, MS Office Spreadsheet 11.0 Memory Leak

Hi,
Can anyone see what I'm doing to cause a memory leak? I am using LabVIEW 2011 (and this happens in 8.2.1 also).
Is the last Close Ref. needed because there's an allocation evey loop?
Is it bad that there's a buffer allocation on the right side of 'Value2'?
I've attached an image and the actual VI.
Thanks,
Albert
Attachments:
Excel_LV2011_CalcFullk.vi.PNG ‏45 KB
Excel_LV2011_CalcFullk.vi ‏12 KB

I added the last Close Ref. because there is a buffer allocation on the ref. input of the Range node, I couldn't think of anything else to do to reduce memory usage, and the close seems to reduce (but not eliminate) memory leakage.
I have the invoke node in the loop to simulate a more complicated situation that seems to be leaking memory and I want to exaggerate problems here so I know what should and should not be done.
I also suspect that I don't really have a good way of checking for memory leaks. All I do is run the VI(s) and then watch Mem Usage for LabVIEW in my task manager. I see memory usage go up 1.M over about 70 minutes but it usually doesn't go up with other VIs.
Is Is there a better way? Should I make a build of this VI and then use software that finds memory leaks?

Memory leak in FormatUtils.formatTimeStatus()

hello smp developers,
i find memory leak in
FormatUtils.formatTimeStatus()
after every call, in memory stay 4 String, 1 Object, 1 Function and 1 Vector.<String>
after recreate local function to external, memory leak gone
and maybe performance issue in ScrubBar.as, for scrubBarLiveOnlyTrack and scrubBarLiveOnlyInactiveTrack
every frame it create 50 BitmapData and 50 Rectangle, even if live track not showing
after change it on "new Sprite()" in configure function, create 50 BitmapData and 50 Rectangle gone
all found in last version of smp
ps bugbase not working anymore http://bugs.adobe.com/jira/browse/ST? I get "PERMISSION VIOLATION"
thx,
mike

thanks Silviu
i create two bugs
https://bugbase.adobe.com/index.cfm?event=bug&id=3341143
https://bugbase.adobe.com/index.cfm?event=bug&id=3341146

Memory leak issue in tuxedo server

Hi,
I am facing memory issues in our tuxedo application.One of the server memory utilization is gradually increasing after reboot. As a temporary solution , we are making restart of that particular server every week.
I have installed Valgrind tool.i am trying to call the service ( Around 800 services are part of application ) which i suspect causing memory leak through ud script. like below.
valgrind ud32 < servicename.ud
but it is not giving memory leak details in actual service instead it is giving details about ud.
Could you guys suggest how can we find memory leak in tuxedo services.
Thanks
Ramana

HI Sir,
Thanks a lot for your response.
I ran the comand as mentioned by you in your post. but i haven't shutdown the server bcoz it is prod environment.
It logged huge output to the log file.
Below is the summary of the logfile.
==00:00:00:05.383 23666== LEAK SUMMARY:
==00:00:00:05.383 23666== definitely lost: 7,105 bytes in 7 blocks
==00:00:00:05.383 23666== indirectly lost: 3,383 bytes in 18 blocks
==00:00:00:05.383 23666== possibly lost: 28,653 bytes in 9 blocks
==00:00:00:05.383 23666== still reachable: 529,286 bytes in 288 blocks
==00:00:00:05.383 23666== suppressed: 0 bytes in 0 blocks
==00:00:00:05.383 23666==
==00:00:00:05.383 23666== For counts of detected and suppressed errors, rerun with: -v
==00:00:00:05.383 23666== Use --track-origins=yes to see where uninitialised values come from
==00:00:00:05.383 23666== ERROR SUMMARY: 107 errors from 72 contexts (suppressed: 10 from 10)
But I am not able to understand the output logfile. Could you please let me know how can we analyze the logfile.
Thanks in advance.

Memory leak in 6.0a2

I am using firefox 6.0a2 on fedora 15.
I am updating firefox daily.
System hangs suddenly after installing addons.

"MichelC" wrote...
> This sounds very much like a reference leak in your program and not
> like a memory leak in LabView (although you wrote that you already
> thought of that)
>
>
>
> - Make sure you terminate all kinds of reference = Vis and files
> references BUT ALSO references to controls and indicators (property
> nodes).
That was exactly the advice I needed. I never realized that I might need to
close references to controls/indicators, but it makes sense. I found a
couple places where a different refnum was being generated on every
iteration of a loop and reworked the code a bit, and now the problem seems
to be solved (fingers crossed).
In case anyone else is interested, the main source of my problem was a
Controls[]
property on a cluster refnum. Every time the loop accessed the
property, it generated a new set of refnums in the Controls[] array. Over
many iterations this led to (presumably) thousands & thousands of orphaned
refnums that were gradually draining my program's will to live.
Thanks for the help!
Regards,
Justin Goeres
Pleasanton, CA

New Memory Leak Detector released

This week we released an updated version of the Memory Leak Detector. It now features a much improved graphical user interface as well as more powerful ways to track down memory leaks.
The tool is designed to help you find memory leaks in production type environments without causing much overhead. It allows you to attach to a running JRockit process, analyze the heap, and detach, leaving the process running at full speed again.
There is an article on dev2dev which describes the tool in more detail: http://dev2dev.bea.com/pub/a/2005/06/memory_leaks.html
Download the free tool today at: http://dev2dev.bea.com/wljrockit/tools.html
Comments are always welcome here in the forum.
Regards,
/Staffan Larsen

FYI, the console ist providing this stack trace in the details window:
java.io.IOException: Unsupported JVM on host 'localhost' at port 7090.
Make sure you are running the correct version of JRockit.
     at com.jrockit.memleak.model_impl.MemleakUtil.handleConnectionException(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil.doConnect(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil.access$000(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil$1.run(Unknown Source)
     at foxtrot.AbstractWorkerThread$2.run(AbstractWorkerThread.java:49)
     at java.security.AccessController.doPrivileged(Native Method)
     at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:45)
     at foxtrot.workers.DefaultWorkerThread.run(DefaultWorkerThread.java:153)
     at java.lang.Thread.run(Unknown Source)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException]
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.findRMIServer(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
     at com.jrockit.memleak.comm.RemoteMLSController.getServerConnection(RemoteMLSController.java:152)

What is memory leak

hi,
can any body tell me wat we mean by "memory leak problm"
its resulting in failure of a process chain.
thanks

Hello,
Memory leaks are created by keeping a reference to objects that are not in use any more. Often, container objects (like the Java Collection Classes) are the source of such leaks. All objects or classes that are used to collect information are candidates for memory leaks. Especially static variables are dangerous, because the class object itself is not released by the garbage collector. This has to be kept in mind when static lists or maps are introduced.
chk this blog:
/people/krum.tsvetkov/blog/2007/07/02/finding-memory-leaks-with-sap-memory-analyzer
regards
GVS

Winverifytrust memory leaks?

I had a question on winverifytrust's catalog signing. We are using winverifytrust and we don't call WTD_ACTION_STATE_CLOSE after the call, we call it only if hWVTStateData is not NULL. What we see is that system memory consumption continues to rise in spikes
The consumption rises, then settles down to a steady state and then rises again after some time and then rises again after a longer period with a larger amount. We believe this may be the side-effect of internal caching done by the catalog signature trust
API. Could someone help confirm the behaviour
1. Is this expected behaviour?
2. Is our usage of the API (not calling STATE_ACTION_CLOSE unconditionally correct?)
3. Does internal caching behave this way, if so does it reach a steady state where the cache size will not grow beyond a certain limit, can that limit be predicted?
Thanks,
Balbir

Hi,
Could you please have a share for which developer language we are using here?
Regarding the issue here, we'd better seek help in some developer forum for a better assistance.
MSDN troubleshooting and support
http://msdn.microsoft.com/en-hk/hh361695.aspx
Meanwhile, we might also take a use with the Windows Performance Toolkit to find memory leaks.
See the blog below:
Using the Windows Performance Toolkit to find memory leaks
Windows 7: Memory Leak Troubleshooting
Please note: Since the websites are not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards
Michael Shao
TechNet Community Support

Finding Memory Leak in LabVIEW

Similar Messages

Maybe you are looking for