Daniel Biesiada
9/30/2005 8:49:00 AM
Joris de Gruyter wrote:
>>Sounds like a terrible memory leak in your code. Have you analyzed your
>>code in that context? Both if you free correctly your objects and if they
>>are correctly initialized on server/client side.
>
>
> Unfortunately there''s no pointers so "freeing correctly" is not something
> people do or need to do.
In visual basic you had no pointers also and garbage collecting showed
that you have to follow some basic best practices not to see your
application working incorrectly in context of memory usage. I''ve
experienced similar thing in Axapta X++ in one past project. I thought
that everything is ok but memory usage in the system seemed to me at
least confusing. After all checks for object references I discovered
that even in X++ it''s just to easy to make a memory leak.
> However, if you want to free up classes before they run out of scope you
> could assign NULL to the object, which will force the garbage collector to
> free up the memory used. But i''m not too sure this will help you all that
> much.
That''s what I meant by freeing correctly. Assigning nulls and checking
if some object referencing doesn''t go out of control.
best regards,
Daniel