Memory Leak.

 

I notice significant memory leaks. Am I using the correct settings? Running this on VB6/WinXP.

On startup: 7Mb. Filled 295Mb. Cleared 50Mb .  Repeated filling never gets above 295Mb, Cleared it hovers around the 50Mb.

 

I'd REALLY like an answer/solution. Sample code below.

 

Jurgen

 

 

Simple form with 2 commandbuttons/1 textbutton/1ReportControl (v13.0.0)

Private Sub Command1_Click()
  Dim i&, n&
  n = Val(Text1)
  With ReportControl1
    With .Records
      .DeleteAll
      For i = 1 To n
        With .Add
          .AddItem "just some text" & i
          .AddItem i
        End With
      Next
    End With
    .Populate
  End With
End Sub

Private Sub Command2_Click()
  With ReportControl1
    .Records.DeleteAll
    .Populate
  End With
  ReportControlGlobalSettings.FreeBatchExtraData
End Sub

 

 

 

 

I'm using a Core2Duo with plenty memory, and it's a very stable machine. (can't remember when it crashed, months and months ago)

I need to dive deeper into this, but I hate the loss of time. Deadline is creeping up on me.

 

I'm using  SuiteControls ocx dated 9 feb 2009. (Both ascii and unicode version give similar results)

Any ideas where or how i should trace this?

 

 

(depending on .UseReportCustomHeap & .UseBatchAllocation & .FreeExtra)

 

Been digging into all kinds of services running on my machine + virtual mem settings)  no differences yet... gotta find me some better digging tools to get to the bottom of this. 

And I still have the memory leak... Core2Duo  with 2Gb interleaved DDR2.   (50Mb taken for an empty form... DAMN. I am going to escalate this.

http://msdn.microsoft.com/en-us/library/aa366525(VS.85).aspx

Hardly my usual stuff, but I'm a terrier, and I want this solved, my app is due on june 1st, and the memory leak will be reason for refusal by my client.

=> meaning I wont get paid until I solve this. I changed from IGrid to CodeJock late in the game, and it set me back by a month. (It's a 14k line project and a demanding project manager for a commercial app.  I'm not too happy to switch to yet another control.

 

I've tried safemode. no luck. but this weekend I'll do ALL the footwork with my hardware. I'll try with 1Gb/2Gb/4Gb and several bios options.. and I'm sure I can dig around for an old VBA card that doesn't use shared memory (IF that is the problem). I'll bloody find the "situational" setting that ReportControl can't manage!

 

No worries, this will continue on monday.

 

 

a) Your suggestion is what MS$ is/was famous for.  It's not a bug, it's a known issue. We'll not fix the bug, but give you a workaround.

 

b) My project is for wide distribution (>15000 users) and we're a small outfit. We decided against using a data provider at the beginning of the project which now stands at 15k lines of code. Our users range from corporations to small business and not all are computer savvy. We prefer spending our support time to functionality and avoid "compatibility and installation issues", thus no caching in databases etc.  My app is due shortly, and my time is precious. With the exception of the memory leak the reportcontrol functions very well. 

 

c) The Virtual list sample in the standard samples: I added an entry form to load and unload the main form. The memory leak is less pronounced (approx 5MB)  but it's still there.

 

d) in the meantime I found an API (EmptyWorkingSet) that reduces the amount of WorkingSet / Private memory by swapping it to the pagefile.

Most users will not notice that I'm cheating.

 

e) I will make an effort to implement virtual mode in the Report that's causing the memory probs(with or witout a disconnected recordset). Ofcourse it happens to be the most complex one in my project with lots of grouping/sorting, conditional coloring, multiple selection etc.   The sample for Virtual List is rudimentary, glancing at how it handles grouping I fear I'll need plenty documentation.. but CJ helpfile is totally useless.

 

I hope to be able to read the support issue soonest. and we'll continue the discussion there. There's plenty of other todo's on my list.

 

Cheerz, Jurgen

When I add an item with a string to my record, the leak is back (or still there)

 

I'm also unhappy with general memory consumption, which is very high at >1KB per record.