unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: JIANG Shaojian <sdycjsj@gmail.com>
To: Akira Kyle <ak@akirakyle.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
	emacs-devel@gnu.org
Subject: Re: [PATCH] Interferences between xwidgets and async processes?
Date: Tue, 17 Aug 2021 23:09:38 +0800	[thread overview]
Message-ID: <CADut6p1J9=nDccEzGmTj20zjVYKrSrrebg3srX_NqztnRCRO1g@mail.gmail.com> (raw)
In-Reply-To: <CADut6p0gaBEwKT8izXugdccEsg4B0XUshmMwkVKDxDmy1YumEA@mail.gmail.com>

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

Hi,

WIth previous patch, I just noticed a message generated by xwidget saying
"Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you
want WebKit to use a different signal".
I did a bit of search and found out that this might be related to a recent
version of libwebkit2gtk (see a similar message in
https://github.com/vertcoin-project/one-click-miner-vnext/issues/271).

The current version of the library on my ubuntu is 2.32. I tried to
downgrade it to an earlier version available, which is 2.28 and the
issue is gone.
So it seems that the updated library breaks previous fix.
Further debugging is beyond my expertise. Hopefully the above information
is useful.

Thanks.


JIANG Shaojian <sdycjsj@gmail.com> 于2021年7月30日周五 上午10:55写道:

> Hi,
>
> I just built emacs 28 with the lasted source, and it seems that this bug
> reappears.
> Since I have not updated emacs for a long time, I am not sure when it came
> back.
> I checked xwidget.c and previous fix is still there.
>
> The testing environment and the way to reproduce it is the same as before.
>
> Hopefully someone can confirm this.
> Thanks!
>
>
> Akira Kyle <ak@akirakyle.com> 于2020年11月15日周日 上午3:53写道:
>
>>
>> On Sat, Nov 14, 2020 at 09:22 AM, Eli Zaretskii <eliz@gnu.org>
>> wrote:
>>
>> >> > The attached patch fixes this but only in a temporary way.
>> >>
>> >> Thanks; applied to Emacs 28.
>> >
>> > Just to be sure: the fix that is now installed on master does
>> > support
>> > current and old versions of Glib, where the old code seemed to
>> > work?
>> > Or does it break with older Glib versions?
>>
>> I didn't explicitly try it with glib versions before they changed
>> the signal handling in commit 2e471acf, but it *should* work with
>> versions before the change. As you can see in the patch, it
>> essentially just makes Emacs more aggressive in taking over the
>> signal handler and in glib versions before 2e471acf,
>> g_source_unref (source) wouldn't result in glib resetting the
>> signal handler to SIG_DFL, in which case Emacs will just install
>> itself twice to handle SIGCHLD which is fine.
>>
>> I think commit 2e471acf got added to glib with version 2.37.5
>> which was released over 7 years ago.
>>
>>

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

  reply	other threads:[~2021-08-17 15:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  3:15 Interferences between xwidgets and async processes? JIANG Shaojian
2020-10-28  8:24 ` Lars Ingebrigtsen
2020-10-28 15:12   ` Eli Zaretskii
2020-10-29  2:43     ` JIANG Shaojian
2020-10-29 14:23       ` Eli Zaretskii
2020-11-05 20:27         ` [PATCH] " Akira Kyle
2020-11-06 15:03           ` Robert Pluim
2020-11-09 13:52           ` Lars Ingebrigtsen
2020-11-12 19:25             ` Akira Kyle
2020-11-14 15:43               ` Lars Ingebrigtsen
2020-11-14 16:22                 ` Eli Zaretskii
2020-11-14 19:53                   ` Akira Kyle
2021-07-30  2:55                     ` JIANG Shaojian
2021-08-17 15:09                       ` JIANG Shaojian [this message]
2021-08-18 14:46                         ` Lars Ingebrigtsen
2020-11-14 19:39                 ` Akira Kyle
2020-11-16 21:38                   ` Lars Ingebrigtsen
2020-11-10  1:23           ` JIANG Shaojian

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='CADut6p1J9=nDccEzGmTj20zjVYKrSrrebg3srX_NqztnRCRO1g@mail.gmail.com' \
    --to=sdycjsj@gmail.com \
    --cc=ak@akirakyle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).