Generally you want to look through heap histograms and check whether the number of `GroovyClassLoader`s is increasing (typically 4 per build IIRC) and never (hard) or rarely (soft) returning to a baseline even after explicit GC. If so, check root references in a memory analyzer (JVisualVM ~ NetBeans profiler, MAT, YourKit, etc.). A confirmed reference chain is enough to file a bug report, especially if steps to reproduce are known.
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2qGi-fKAYbC%3DnG9Mk_Qb0GQqfzk-tAOhbrka8Su%2BVZ5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
