This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
While developing a debugger for my proprietary language, I've noticed a that with the Debugger framework there is a problem with the variable validation. As variables are created they are added to the validator for that debugging session. However, variables are never removed from the validator when calling into another call stack scope or when leaving the call stack scope. This leaves overhead that continously grows throughout a degugging session. Each time you call into another call stack scope, all of the old variables will be validated for the scope ( valid or not ) and then when leaving that call stack scope, all of the newly added variables are added to the validation that occurs for each line of code.
There should be weak reverence from Validator to variable. But me be there is some problem. I will look at it soon, but I can not promise that it will be fixed to nb3.5.
The problem is that local variables are not removed from the validator immediately after they go out of scope. They should, however, be removed by the garbage collector later. In any case, I consulted the it with Jan and we agreed that this issue does not affect rainier because 1) it only affects java local variables 2) watches are removed from the validator after they are deleted from the watches view. Also, examining the rainier runtime behavior leads me to conclusion that it does not call validate() method of the Validator anyway. I'm removing the rainier keyword.
The weak mapping does not seem to work properly, we need to rewrite the validating engine for the new debugger => promoD.
fixed in the main trunk. Validation of variables has been rewritten completely.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.