Information générale
Catégorie:
Programmation Orientée Object
Titre:
Dangling data session
Hello,
I have read a lot here about this subject, but I am still at a loss with the following problem. I am creating cursors and custom objects in a private data session, I release all of them (or I rather think I do), and the data session won't go away. I can check that there is no cursor any more in the data session, and no object is shown in DISPLAY MEMORY. No transaction as all this is against a remote database.
Class definitions for the custom objects are in a prg, if I modify this prg I get the "remove classes from memory?" question, and if I answer yes my data session goes away. So what was making the data session persist was clearly an object of one of the 10 classes defined there. But how can I find out this resilient object ? DISPLAY MEMORY doesn't show it.
If there is no direct way to do it, I could try to check whether every =null on my objects has been succesful. Is the firing of the Destroy event the correct indicator for that ? Does it work with collections too ?
Unfortunately I didn't manage to reproduce this problem with a simple example. But I would be very thankful for any hint on how to investigate the problem.
David
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement