Trace view: Changing the depth doesn't cancel the existing processing

[laksono]

Steps to reproduce:

• Open a database with huge traces
• Changing the depth very rapidly
• The change of depth doesn't kill the current process

This causes an error when exiting the application

The following call stack shows some threads are stuck and not killed

Thread [pool-24-thread-11] (Suspended)  
    Thread.sleep(long) line: not available [native method]  
    DetailPaintThread(BasePaintThread).call() line: 95  
    DetailPaintThread(BasePaintThread).call() line: 1   
    FutureTask<V>.run() line: 264   
    ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1128  
    ThreadPoolExecutor$Worker.run() line: 628   
    Thread.run() line: 834  
Thread [pool-24-thread-16] (Suspended)  
    Thread.sleep(long) line: not available [native method]  
    DetailPaintThread(BasePaintThread).call() line: 95  
    DetailPaintThread(BasePaintThread).call() line: 1   
    FutureTask<V>.run() line: 264   
    ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1128  
    ThreadPoolExecutor$Worker.run() line: 628   
    Thread.run() line: 834  

[blue42u]

This repository has moved to GitLab, please continue this issue there.