GNU bug report logs - #25247
26.0.50; Concurrency crashes

Previous Next

Full log

Message #68 received at 25247 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Elias Mårtenson <lokedhs <at> gmail.com>
Cc: raeburn <at> raeburn.org, 25247 <at> debbugs.gnu.org, tino.calancha <at> gmail.com
Subject: Re: bug#25247: 26.0.50; Concurrency crashes with XLib
Date: Sat, 31 Dec 2016 13:05:41 +0200

> From: Elias Mårtenson <lokedhs <at> gmail.com>
> Date: Fri, 30 Dec 2016 19:21:08 +0800
> Cc: Tino Calancha <tino.calancha <at> gmail.com>, raeburn <at> raeburn.org, 25247 <at> debbugs.gnu.org
> 
> One interesting fact is that if I replace ‘sleep-for’ with ‘sit-for’, then the updates come at exactly the expected
> time.

But only as long as blink-cursor-mode is turned on, right?  If you
turn it off before running the experiment, sit-for behaves the same as
sleep-for, right?

When blink-cursor-mode is ON, it supplies 2 events each second, and
that allows the threads that finished waiting to acquire the global
lock and insert the string.  Otherwise, the threads wait for the
global lock and do the insertions at the end.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.