Memory increasing in LV2009 but not in LV8.5

[andrej]

Hi.

I have developed application that is very simple. It opens 20 references of .NET object, call .NET method and close all 20 references. This is repeated every iteration. I am developing this application in Labview 8.5 but it will run in Labview 2009. So I am testing it in Labview 2009 evaluation. After one day application have crashed because of "Labview memory is full". I have noticed that memory is increasing constantly if application is running. Then I ran the same application in Labview 8.5 and memory usage has not changed since start (application is running for 3 days now). Is this because Labview 2009 is in evaluation mode or is problem somewhere else?

Thanks,

andrej

[Broken_Arrow]

No help, but I also have a memory leak with a project that has .NET references. I am using 2009 f2. Depending on the device the software is talking too, I can turn off the .NET code, and when I do that, there's no memory leak.

I didn't check this back on 8.6 or 8.5, so I'm not sure if it's a new problem.

[aeastet]

This is a real issue that NI is aware of and the have a CAR open for this issue. See the attached forum.

http://forums.ni.com/ni/board/message?board.id=170&thread.id=445095&view=by_date_ascending&page=1

[Ben]

that thread said it is fixed with the f2 patch but Broken indicates he has f2.

So..

New bug

Bug not fixed

or Broken does not have f2.

Curious,

Ben

[Broken_Arrow]

---

Ben wrote:

that thread said it is fixed with the f2 patch but Broken indicates he has f2.

So..

New bug

Bug not fixed

or Broken does not have f2.

Curious,

Ben

---

Message Edited by Broken Arrow on 12-16-2009 10:46 AM

[Ben]

---

Broken Arrow wrote:

---

Ben wrote:

that thread said it is fixed with the f2 patch but Broken indicates he has f2.

So..

New bug

Bug not fixed

or Broken does not have f2.

Curious,

Ben

---

Message Edited by Broken Arrow on 12-16-2009 10:46 AM

---

So...

New bug

or

No fix

Ben

[Broken_Arrow]

My memory leak is slow enough - and our need for the software to access to the .NET stuff is rare enough - that I haven't looked into the issue. My program will run for a few days with no problem. It may start off at 480MB and be at 650MB 48 hours later. 

However, I must say that I'm not convinced it's the bug if the bug has been known to be fixed on f2. Reason is, the .NET vi's were supplied by a vendor, and upon my cursory glance at them, they appear to be a collection of turd balls. There could be references they are not closing, etc. I am closing what I use, but there could be other things going on inside them turds.

[Jarrod_S.]

The bug fixed in f2 refers to .NET callbacks, not to simply opening and closing .NET references. I don't know of any CAR on that.

[andrej]

I have installed patch f2 but memory leak still remains.

[andrej · Accepted solution]

I wrote my previous post a little bit to fast. After additional testing I can confirm that there is no memory leak in my application after I installed patch f2.