invokeMethod's result gced immediately
Egor Ushakov
egor.ushakov at jetbrains.com
Thu Mar 12 10:12:49 UTC 2020
Hi all,
it seems that the result of the invokeMethod could be gced immediately,
which is quite strange.
Currently we have to do:
invoke + disableCollection
new(Array)Instance + disableCollection
(String)mirrorOf + disableCollection
in a loop until succeeded, to allow something like foo().boo().zoo() to
evaluate successfully.
Is there a way to automatically disable collection for newly created
objects from jdi?
Maybe there's a bug about this?
Thanks!
--
Egor Ushakov
Software Developer
JetBrains
http://www.jetbrains.com
The Drive to Develop
More information about the serviceability-dev
mailing list