Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

Memory leak reported by Plumbr #123

Closed
rsignell-usgs opened this issue Apr 17, 2015 · 2 comments
Closed

Memory leak reported by Plumbr #123

rsignell-usgs opened this issue Apr 17, 2015 · 2 comments

Comments

@rsignell-usgs
Copy link
Contributor

rsignell-usgs commented Apr 17, 2015

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()

@lesserwhirls
Copy link
Collaborator

@rsignell-usgs - Plumbr looks like a very interesting tool! Do you see this same issue using the 4.6.1 stable release?

@rsignell-usgs
Copy link
Contributor Author

I no longer have Plumbr, so closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants