VB6 memory leak from CreateObject -


i'm using eternal library (dll) load in file format , have found out load function doesn't load. load first time it's called same object if call again open new file doesn't load. has forced me call createobject each time want load new file. problem vb6 doesn't seem free old object @ , ram , vm usage bloats gbs.

is there way force free up? setting variable "nothing" or "null" doesn't , app bloat run out of memory , crash. (i have run inside vm since ide old doesn't work on win7, couldn't work)

i've looked circular references there aren't any, file loaded using object, properties of file read ado object, , actual file never referenced ado object, various fields it.

whether have direct reference in vb6 project or use "createobject" instantiate object reference not matter. if third party component has memory leak you'll experience same behaviour either way.

if instantiating unmanaged resource need call "dispose". other that, object instance fall "out of scope" when method call has completed , visual basic runtime shall clean reference (using reference counting). if third party component indeed have memory leak you'll need have them patch dll there nothing can prevent it.


Comments

Popular posts from this blog

django - How can I change user group without delete record -

java - Need to add SOAP security token -

java - EclipseLink JPA Object is not a known entity type -