From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Philippe <philippe.raven@gmail.com>
Subject: Re: Bug in libX11 or something near ?
Date: Sun, 23 Jun 2019 17:57:00 -0000 [thread overview]
Message-ID: <5fa8b89e-1a9d-2619-f49f-c1680d587148@dronecode.org.uk> (raw)
In-Reply-To: <CAC-34C0eHbNVnKT9HV1JGd3MJ4R=njABKWavXkiYLAUkjcXvKQ@mail.gmail.com>
On 18/06/2019 17:07, Philippe wrote:
> I'm using Cygwin/X and identified a critical bug using some piece of
> software.
> I don't really know where to begin, but I'm able to crash some applications
> via the application's menu, only with Cygwin/X (no crash with Xming, and no
> crash under any Linux distributions).
>
> For information, It goes through VirtualGL. I'll give the example on how to
> reproduce it with a free software : Paraview (under linux).
>
> So you open Paraview, then clic on "View" > show the "Toolbars" submenu,
> then you move your mouse directly on the "Sources" or "Edit" menu, then it
> crashes immediately. The only error message in the linux shell (from where
> it was launched) is "paraview: Fatal IO error: client killed".
>
> I got those lines in the XWin.0.log file :
> SetupSysMenu: GetSystemMenu() failed for HWND 0x130746
> winTopLevelWindowProc - WM_DESTROY - WM_WM_KILL
Thanks for reporting this problem, and the clear reproduction steps.
This is an interesting bug in the Cygwin X server's multiwindow mode. It
seems that under some circumstances, when removing a WM_TRANSIENT_FOR
window which in turn had a child WM_TRANSIENT_FOR window (e.g. a menu
which has a sub-menu), the X server's integrated WM would get confused
and think that the main window had been closed (so terminating the
application).
I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps
you could try that and see if it improves things for you?
(I guessed you are using 64-bit Cygwin. If you need a 32-bit build
instead, please let me know and I'll generate one)
[1]
ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20190623-git-210c90b328cf8f18.exe.bz2
--
Jon Turney
Volunteer Cygwin/X X Server maintainer
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-06-23 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 16:08 Philippe
2019-06-23 17:57 ` Jon Turney [this message]
2019-06-23 18:41 ` Philippe
2019-06-24 7:28 ` Philippe
2019-06-25 11:15 ` Jon Turney
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=5fa8b89e-1a9d-2619-f49f-c1680d587148@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=philippe.raven@gmail.com \
/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.
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).