Just for history. No hidden bug. It was an race condition introduced by
my code. Fix has been integrated for this issue...
https://pharo.fogbugz.com/default.asp?14874
cheers -ben
On Sat, Feb 7, 2015 at 1:08 AM, Ben Coman b...@openinworld.com wrote:
My first thought is that it may expose some
On 05 Feb 2015, at 21:34, Max Leske maxle...@gmail.com wrote:
On 05 Feb 2015, at 17:46, Ben Coman b...@openinworld.com
mailto:b...@openinworld.com wrote:
On Thu, Feb 5, 2015 at 11:12 PM, GitHub nore...@github.com
mailto:nore...@github.com wrote:
Log Message:
---
+1
STef
Le 5/2/15 21:34, Max Leske a écrit :
On 05 Feb 2015, at 17:46, Ben Coman b...@openinworld.com
mailto:b...@openinworld.com wrote:
On Thu, Feb 5, 2015 at 11:12 PM, GitHub nore...@github.com
mailto:nore...@github.com wrote:
Log Message:
---
40477
I see it as well from time to time in #40478 but not often and it does not seem
to have any negative effect, I can just keep on working and there is no obvious
slowdown.
On 06 Feb 2015, at 16:23, Marcus Denker marcus.den...@inria.fr wrote:
On 06 Feb 2015, at 09:07, Marcus Denker
On Thu, Feb 5, 2015 at 11:12 PM, GitHub nore...@github.com wrote:
Log Message:
---
40477
14669 Delay refactoring (part 2a) - avoid UI locking up when timer event
loop is stopped
https://pharo.fogbugz.com/f/cases/14669
Thanks Max and Marcus for review and pushing
On 05 Feb 2015, at 17:46, Ben Coman b...@openinworld.com wrote:
On Thu, Feb 5, 2015 at 11:12 PM, GitHub nore...@github.com
mailto:nore...@github.com wrote:
Log Message:
---
40477
14669 Delay refactoring (part 2a) - avoid UI locking up when timer event loop
is
