From: Liam Quinlan <liamkquinlan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: --with-cairo Emacs server crash and fix
Date: Tue, 13 Aug 2019 13:36:23 -0400 [thread overview]
Message-ID: <CAAQqQ-2DSx9f-sW9ep-myynCT6wCTx1aT7UH0v3BO_cE=42s1A@mail.gmail.com> (raw)
In-Reply-To: <83mugdrtz6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
Alright cool. I'll have a look at your changes for comparison. Thanks for
the explanation.
On Tue, Aug 13, 2019, 11:00 Eli Zaretskii, <eliz@gnu.org> wrote:
> > From: Liam Quinlan <liamkquinlan@gmail.com>
> > Date: Mon, 12 Aug 2019 22:52:31 -0400
> > Cc: emacs-devel@gnu.org
> >
> > Update: i think I've found the actual proper solution. Alternative
> patch on offer below; this time by checking for
> > dynamic bitmaps already in place after finishing the static ones in
> x_cr_init_fringe. Note that that function also
> > defines w32_init_fringe if HAVE_NTGUI, so windows is covered.
>
> Yes, the idea is correct, but the implementation needed some tweaking,
> in particular due to w32 doing things a bit differently during
> startup. See commit c90975f on the master branch.
>
> > Trying to be minimal so this example doesn't iterate to over
> fringe_bitmaps looking for sparse elements, just
> > begin checking fringe_bitmaps for existing elements at the index
> following the standard bitmaps leaves off and
> > continue until the first null. I'm not sure if it's too bold to trust
> that holes haven't had a chance to arise though.
> > (perhaps if the server is initially used in console mode and packages
> get unloaded before a gui client
> > connects...?).
>
> No, we cannot assume there are no holes, you can clearly see in
> destroy_fringe_bitmap that it leaves holes if the destroyed bitmap is
> not the last one in the array. So we need to initialize all the
> user-defined bitmaps whose pointer is not NULL.
>
> Btw, there's a simple way of reproducing the problem without any init
> files and extra packages:
>
> emacs -Q -daemon
> emacsclient SOME-VERSIONED-FILE-UNDER-GIT
> M-x set variable RET diff-font-lock-prettify RET t RET
> [modify the file and then save it]
> C-x v =
>
> Before the change I pushed the above would fail to display the vc-diff
> bitmaps on the fringe (I presume the Cairo build will crash). After
> the change, the bitmaps are displayed correctly. This happens because
> diff-mode is loaded before the GUI frame is created, and thus the
> fringe bitmaps defined by diff-mode during loading are not completely
> initialized.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 2803 bytes --]
next prev parent reply other threads:[~2019-08-13 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 15:40 --with-cairo Emacs server crash and fix Liam Quinlan
2019-08-10 9:39 ` Eli Zaretskii
2019-08-12 10:42 ` Liam Quinlan
2019-08-12 10:48 ` Liam Quinlan
2019-08-12 16:59 ` Eli Zaretskii
2019-08-12 20:00 ` Liam Quinlan
2019-08-13 2:52 ` Liam Quinlan
2019-08-13 15:00 ` Eli Zaretskii
2019-08-13 17:36 ` Liam Quinlan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-08 7:01 Liam Quinlan
2019-08-09 7:11 ` Eli Zaretskii
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='CAAQqQ-2DSx9f-sW9ep-myynCT6wCTx1aT7UH0v3BO_cE=42s1A@mail.gmail.com' \
--to=liamkquinlan@gmail.com \
--cc=eliz@gnu.org \
--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.