Yet another memory leak fixed

[Samapico]

When you created maps, then closed them, the memory usage would not drop back down to normal...

 

Problem was:

 

The map form uses a bunch of child classes (lvz, regions, line, testmap, selection, etc.)

When initializing, the map form calls 'setParent' on each of these, which tells them to keep a reference to the map form.

 

When unloading the form, it does terminate all these classes, but the reference stayed there, so the garbage collector would not clear it from memory, since it still had a reference.

 

Bleh. You can try it at home; open the task manager and watch memory usage. Create 10 empty maps, close them. Create 10 more, close them. Repeat until you're out of memory

 

Was going to test the memory usage of the new layered display system I want to do, and I noticed that... good thing I find the problem quickly

[CRe]

Did you fix it doc captain?

[Samapico]

Read the !@#$%^&*le, yes

 

 

 

and call me captain

[Drake7707]

oh yeah, i read that circular references between objects makes the reference counter of the object incorrect, causing the garbage collector not cleaning the object

[Samapico]

We might just have read the same article lol

 

http://www.vbi.org/Items/article.asp?id=106

[Drake7707]

nope

 

http://www.vbaccelerator.com/home/vb/Code/...ces/article.asp