From: Herwig Hochleitner <herwig@bendlas.net>
To: emacs-devel@gnu.org
Subject: Re: Possible issue with mutexes
Date: Wed, 10 Apr 2019 05:11:36 +0200 [thread overview]
Message-ID: <60468e7f-57a8-a263-a004-884b51461db7@bendlas.net> (raw)
In-Reply-To: <c0e06d75-9994-7024-e9a6-f2707159d2ff@bendlas.net>
On 4/10/19 4:57 AM, Herwig Hochleitner wrote:
> Hello,
>
> I've recently created a semaphore type, based on mutex and condition
> vars, for controlling parallelism in an elisp processor.
>
> The project went well, so far, but now that I attempted to pull out
> this semaphore implementation and create a test for it, I've noticed
> behavior, that leads me to believe, that emacs' thread and mutex
> guarantees might not hold in all cases.
>
> When running the [test
> case](https://github.com/webnf/semaphore.el/blob/306d5a84b99526213c3a7d367f8d8041961ea52a/test/emacs-semaphore-test.el),
> you would expect `test/semaphore/active-count` to be 0 at the end of a
> run, right? For me, it's wildly inconsistent at the end of a run and
> seems to become desynchronized among worker threads. In this [example
> run](https://hastebin.com/wigiwizabi.log) from my machine, it happens
> to settle at 10.
>
> Am I doing this wrong, somehow?
>
> If not, could somebody help me file a report? First post on this ML ...
>
> kind regards
Argh .. found the bug in my code.
Sorry for the spam!
Since we are here already, let me ask you about this other issue, I had:
Waiting on a condition var or joining a thread on the main thread can
freeze emacs totally dead. Like kill -9 dead.
Is this a known issue or should I investigate further?
next prev parent reply other threads:[~2019-04-10 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 2:57 Possible issue with mutexes Herwig Hochleitner
2019-04-10 3:11 ` Herwig Hochleitner [this message]
2019-04-10 14:27 ` Eli Zaretskii
[not found] ` <79bd1b97-13e8-a761-04f8-417204a7df29@bendlas.net>
[not found] ` <83y34h6gkb.fsf@gnu.org>
2019-04-10 16:15 ` Herwig Hochleitner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60468e7f-57a8-a263-a004-884b51461db7@bendlas.net \
--to=herwig@bendlas.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.