From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 6E6883858405 for ; Sat, 30 Apr 2022 02:07:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6E6883858405 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 23U272kn056101 for ; Fri, 29 Apr 2022 19:07:02 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpd1DQn19; Fri Apr 29 19:06:54 2022 Subject: Re: Window flickering problem in XWin multiwindow mode To: cygwin@cygwin.com References: From: Mark Geisert Message-ID: <38faf684-7c40-17d7-c961-ce66abc9b74a@maxrnd.com> Date: Fri, 29 Apr 2022 19:06:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2022 02:07:09 -0000 Hello, S.J. Luo wrote: > SL on Apr 26, 2022: > >> I have some EDA tools running on a Linux machine and display on my Windows >> PC using xorg-server-21.1.3 XWin multiwindow mode >> Sometimes the application window flickers forever for an unknown reason. >> The problem became more severe after my PC upgrade to Windows10. > >> After re-compiling and debugging, I found a calling loop triggered. >> Knowing the root cause, I am now able to demonstrate the issue with a small >> test case as well as a patch that works for me. Both are attached below. > > Any one successfully duplicated the issue? I've reproduced it. That's a really annoying effect/issue you're seeing. I've been waiting for the Cygwin X maintainer to respond. I'm not familiar enough with X internals to know whether your patch is the most appropriate fix. I will try to build the object you're patching, with your patch, and make that available to you as a workaround. I'm assuming you haven't done that yourself just yet.. Give me a day or so to work it out. ..mark