Fix object creation tracking #426
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR,
ObjectCreationTransformer
injectedInjections::afterNewObjectCreation
only on the objects on whichObject::<init>
constructor was called. However, if the instrumented code created a new instance of someDerived
class, such that itsBase
class is not instrumented, then noObject::<init>
constructor call would be tracked by the current algorithm (since onlyDerived::<init>
will be called from the instrumented code).To fix this issue, we now track any
::<init>
constructor call, and keep a counter of uninitialized objects to distinguish between actual constructor calls, and the calls of the base class constructor from the derived class constructor.