It's been plaguing me as well. I can't work out if it's the task themselves hanging, a failure in communication between the backend and the front-end or what...
If anyone can add some clues or data points, it would be helpful. It might also be useful in the mean time to implement some kind of force-kill mechanism to the task manager to kill rogue threads and spawn new ones. Adam K On 30 November 2010 23:16, Ahmad Zawawi <ahmad.zaw...@gmail.com> wrote: > Hi, > This bug has been really annoying me since the debut of our dear Task 2.0 > API. It renders Padre literally unusable after opening multiple files and > switching between them. Any ideas? :) > Padre Task manager fails to run tasks after stress testing it > http://padre.perlide.org/trac/ticket/1068 > Regards, > Ahmad M. Zawawi > azawawi > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
