[concurrency-interest] regarding synchronized command and object's footprint

Yechiel Feffer yechielf at gigaspaces.com
Sun Mar 4 04:56:13 EST 2012

I heard a claim that execution of synchronized(object)  command  (maybe contended synchronized) raises the  object footprint in the java heap- a raise the (partially ?) remains even after all threads exited the synchronized block.
Is it correct ? Is it related to barrier info java maintains ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20120304/f289498d/attachment.html>

More information about the Concurrency-interest mailing list