unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25172@debbugs.gnu.org, "Clément Pit--Claudel" <clement.pit@gmail.com>
Subject: bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour)
Date: Thu, 15 Dec 2016 00:12:48 +0800	[thread overview]
Message-ID: <CADtN0WJRgLL0PJdeChJJaUZS-+BB1gU5Z-1ko_HqvsYsiWWmMA@mail.gmail.com> (raw)
In-Reply-To: <83pokua474.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On 15 December 2016 at 00:03, Eli Zaretskii <eliz@gnu.org> wrote:


> Thanks.  Does the patch below help in any way with these crashes?
>
> If not, it sounds like I'm out of my depth here.  The crashes you show
> are deep in the bowels of Glib called by GTK; reading the (annoyingly
> minimal) documentation of those APIs, I sense the danger of some basic
> issue with calling these APIs from several threads.  If what the GTK
> documentation tells everything there is to it, then the patch below
> should fix these problems.  But if not, then I guess we will need help
> from a GTK expert.
>

After applying that patch, it hasn't crashed yet. So either it fixes the
problem, or it's simply buch harder to reproduce. So far so good. Thanks a
lot!

Regards,
Elias

[-- Attachment #2: Type: text/html, Size: 1154 bytes --]

  reply	other threads:[~2016-12-14 16:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 16:35 bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour) Elias Mårtenson
2016-12-11 16:47 ` Andreas Schwab
2016-12-11 16:49   ` Elias Mårtenson
2016-12-11 17:54   ` Eli Zaretskii
2016-12-11 17:52 ` Eli Zaretskii
2016-12-11 19:05   ` Clément Pit--Claudel
2016-12-12  4:50     ` Elias Mårtenson
2016-12-12 17:37       ` Eli Zaretskii
2016-12-13  2:38         ` Elias Mårtenson
2016-12-13  3:40           ` Eli Zaretskii
2016-12-13  3:45             ` Elias Mårtenson
2016-12-13  4:11               ` Elias Mårtenson
2016-12-13  4:14                 ` Elias Mårtenson
2016-12-13  4:16                   ` Elias Mårtenson
2016-12-13 16:26                     ` Eli Zaretskii
2016-12-14  2:58                       ` Elias Mårtenson
2016-12-14  3:00                         ` Elias Mårtenson
2016-12-14  3:02                         ` Elias Mårtenson
2016-12-14 16:03                         ` Eli Zaretskii
2016-12-14 16:12                           ` Elias Mårtenson [this message]
2016-12-15  3:30                             ` Elias Mårtenson
2016-12-15 16:22                               ` Eli Zaretskii
2016-12-15 16:28                                 ` Elias Mårtenson
2016-12-15 16:59                                   ` Eli Zaretskii
2016-12-13 16:23                   ` Eli Zaretskii
2016-12-13 18:25                     ` Andreas Schwab

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADtN0WJRgLL0PJdeChJJaUZS-+BB1gU5Z-1ko_HqvsYsiWWmMA@mail.gmail.com \
    --to=lokedhs@gmail.com \
    --cc=25172@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).