What do you mean by 'livelock' ? I would assume you mean 'the Pharo UI becoming unresponsive', right ? Pharo is properly multithreading, but (1) it is pretty easy to do something so that the UI thread is busy (2) it is pretty easy to do enough work in another thread so that things get very slow In both cases, Pharo would feel pretty dead, but it technically is not (completely)

On 16 Oct 2015, at 06:13, Robert Withers <robert.w.withers@gmail.com> wrote:

I've noticed my image livelocks occassionally, when running tests from a category and other times as well. So when I am in my system, which is crazy with asynchronous evaluation, and I livelock, I wonder: is this due to Pharo locking as I have seen or is there an issue in my code?

Has there been previous reports of livelock? Any clues where the issue may reside?

thanks ^^ Robert