Late cleanup of stack objects

[Arnaud Masson]

In the sync case, the big buffer is retained in heap during the slow IO (until it eventually returns), even if it’s not needed anymore.

Are you sure you see an issue there once this code is warmed up? If so, are you running this in the IDE with the debugger (asking because the debugger need to access locals will prevent the compiler from pruning locals).


I just execute the main() entry once _without_ debugger (from IDE).
I then check memory usage in VisualVM, and I force GC a few times to be sure memory is really retained.
The async app releases the big buffer but not the sync app. (The sync app releases memory if I uncomment the null assignment.)

By warmed-up, you mean it has been JIT-ed? It’s a bit outside the control of a normal app, is it really supposed to have such an impact on object strong ref lifetime?

thanks
Arnaud

Unless otherwise stated above:

Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 069 390,60 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20221105/08967297/attachment-0001.htm>