Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destruction of POPObjects passed as parameters is too extreme #14

Open
BeatWolf opened this issue May 10, 2018 · 0 comments
Open

Destruction of POPObjects passed as parameters is too extreme #14

BeatWolf opened this issue May 10, 2018 · 0 comments

Comments

@BeatWolf
Copy link
Member

When passing a POPObject as a parameter it is disconnected at the end of the method.
This can be avoided by calling makePermanent() on the POPObject, which is done automatically if the javaagent detects that the object is assigned to any variable.

The problem is that this does not work when the object is for example put into a map or list and used at a later moment from a different method. At this point the object is disconnected.

It also throws a hard to understand nullpointer exception which should give a clearer error message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant