this is totally off topic but i once tracked down a serious bug with
ProgressMonitor on OS X. PM uses a JProgressBar, and JProgressBar's UI
is implemented (on OS X) with a thread which, once the JPB is gone,
continues to exist and churn out bar-update events. my app uses a lot
of PMs, and every one would leave a thread in memory churning out these
events, eventually resulting in app slowdown and OOM exceptions.
my workaround was to not use AquaProgressBarUI. instead i use the old
(ugly) BasicProgressBarUI. i've been told this is a longstanding bug of
which apple is aware. if that is true, it's sad that they haven't fixed
it.
