[JIRA] (JENKINS-55900) Java memory mishandling identified

[e.bulatni...@gmail.com (JIRA)]

Title: Message Title

Yevhen Bulatnikov commented on JENKINS-55900   Re: Java memory mishandling identified Oh, finally I see what's the point of creating new arrays constantly.  @CopyOnWrite private volatile float[] history; Documentation of this annotation states:  Represents fields that are protected for concurrency by the copy-on-write semantics. Fields marked by this annotation always holds on to an immutable collection. A change to the collection must be done by first creating a new collection object, making changes, then replacing the reference atomically. This allows code to access the field without synchronization, and greatly reduces the risk of dead-lock bugs. The field marked with this annotation usually needs to be marked as volatile. So this is not so trivial to fix that I thought. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.