You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
I'm running Plumbr which monitors our thredds server for problems. I got this heap leak reported on our TDS Version 4.6.0 - 20150326.1318 and I'm providing it here in case it's useful. Is this useful, or useless?
The memory leak detected is caused by a programming error.
The following information indicates the location of the leak in the source code
At the time the leak was detected, 244 objects existed of class
java.awt.image.BufferedImage
These objects had been created at
uk.ac.rdg.resc.ncwms.graphics.ImageProducer.createImage(uk.ac.rdg.resc.ncwms.graphics.ImageProducer$Components, java.lang.String):243
and were being held
in elementData of java.util.ArrayList
in renderedFrames of uk.ac.rdg.resc.ncwms.graphics.ImageProducer
in a local variable defined in uk.ac.rdg.resc.ncwms.controller.AbstractWmsController.getMap()
The text was updated successfully, but these errors were encountered:
I'm running Plumbr which monitors our thredds server for problems. I got this heap leak reported on our TDS Version 4.6.0 - 20150326.1318 and I'm providing it here in case it's useful. Is this useful, or useless?
The text was updated successfully, but these errors were encountered: