L
Lieven De Foor
Guest
Ensuring Dispose() gets called explicitly for MdiChildren (for which it is not called automatically) and child controls of a UserControl (for which it should work automatically, perhaps this is a bug in Progress.Windows.UserControl
ispose()?) seems to fix most of our problems, assuming all classes have the "components" IContainer added to ComponentsCollection. We did not need to add any explicit DELETE OBJECT statements, for now... On the other hand we found something very alarming: apparently the client log setting influences when the destructor of our forms and child controls fires. With client log on (at least 4GLTrace level basic) everything works as expected. With client log turned off, we do NOT get the destructor of our forms and child controls (we get it at the close of the session). This means the no forms/controls get garbage collected completely... I've added this finding to a technical support case to investigate our memory issues.
Continue reading...
ispose()?) seems to fix most of our problems, assuming all classes have the "components" IContainer added to ComponentsCollection. We did not need to add any explicit DELETE OBJECT statements, for now... On the other hand we found something very alarming: apparently the client log setting influences when the destructor of our forms and child controls fires. With client log on (at least 4GLTrace level basic) everything works as expected. With client log turned off, we do NOT get the destructor of our forms and child controls (we get it at the close of the session). This means the no forms/controls get garbage collected completely... I've added this finding to a technical support case to investigate our memory issues.Continue reading...