Detangler finds the main cause of slow Swing apps.

It shows you the exact lines called in the wrong thread, so it's easy to fix it fast.

Which Swing components are thread safe? None.

It turns out the old rules were wrong. After years of confusion about which parts of Swing are thread safe, here's the definitive word from Sun:

Like almost all of us, you probably didn't write your code with that in mind. That means bugs. Detangler finds them.

People sometimes still try to identify a few thread safe calls. But again and again the supposedly safe calls have turned out not to be. The safe and simple assumption is that none are thread safe.

You don't have to change a single line of code to use Detangler.

All you need is debugging on when you compile.

Detangler also finds:

These bugs are usually caused by incorrect Swing threading. And thread bugs are the hardest to find.

Detangler finds those tough bugs for you. So your app runs fast and smooth.

JavaFX, Groovy, JRuby, Scala and Jython all need Detangler

JavaFX is based on Swing. The others all use Swing internally.

SWT uses the same single thread model, but Detangler won't help you there.

How to use Detangler

Detangler is the easiest way to find the hardest Swing bugs. It finds the main cause of slow Swing apps.