>>My problem was that I was storing reference of another object into the property of the business object I wanted to release. The other object could not release because of some other issue so it held up my bizobj in the memory.
>>
>>Makes sense?
>
>Yes, I believe, this is exactly what is happening in our case as well. Since Chris confirmed my observation, it means, we found a bug in the framework. Strange, that nobody found it before. But now we have to find the culprit and it would be very hard, I'm afraid.
A trick I have used is to assign an object
name a character value right after the release. Some visual objects lag when they are released - in that case I set the visible to false before release.
myObject.release
myObject="X"
Imagination is more important than knowledge
