No not that one. I did read in the java dev list that the swing progress bar component does spawn it's own threads for the animation and sometimes does forget to clean up this extra background thread. I thought if one could replace all progress bar components with a simple text label one that only display the percentage text one could check if the progress bar component is the culprit of the memory problem.