From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109034 invoked by alias); 24 Apr 2018 21:30:54 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 107801 invoked by uid 89); 24 Apr 2018 21:30:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_20,KAM_LAZY_DOMAIN_SECURITY,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=Centre, dept, Canada, canada X-HELO: cliff.scrc.umanitoba.ca Received: from cliff.scrc.umanitoba.ca (HELO cliff.scrc.umanitoba.ca) (140.193.42.125) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 24 Apr 2018 21:30:04 +0000 Received: from cliff.scrc.umanitoba.ca (cliff.scrc.umanitoba.ca [140.193.42.125]) (authenticated bits=0) by cliff.scrc.umanitoba.ca (8.14.7/8.14.7) with ESMTP id w3OLU1Wj004164 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 24 Apr 2018 16:30:01 -0500 Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash From: Gilles Detillieux To: cygwin@cygwin.com References: <30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca> Message-ID: Date: Tue, 24 Apr 2018 21:30:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-04/txt/msg00304.txt.bz2 I just ran into this bug on a third Windows 10 1709 64-bit system, only this time it was a little worse. Both xwin-xdg-menu.exe and xterm.exe would crash. An strace on xterm.exe showed the crash occurring after reading that same font, but it happened even when I reverted libharfbuzz0 to the 1.7.4-1 version. On this system, I also had to revert libfreetype6 from 2.8.1-1 to 2.6.5-1 to get xterm and xwin-xdg-menu to run reliably. Something in the font handling in these two libraries broke on a recent update. On 04/19/2018 04:15 PM, Gilles Detillieux wrote: > Has anybody else run into this problem? I've done two installations of > Cygwin/X on Windows 10 systems this week, and they both had problems > with the XWin Server dying just a few seconds after starting up. I > traced the problem back to xwin-xdg-menu.exe getting a Segmentation > fault, which then causes XWin Server to exit. I hacked an alternate > .startxwinrc file to prevent XWin Server from dying (it ends with a > "sleep infinity"), so I could debug it further. > > With the XWin Server running reliably, I then ran "strace > xwin-xdg-menu.exe" and saw that it got a segmentation fault just after > reading a TTF font from the Windows Font directory (bahnschrift.ttf if > it matters). I noticed there were two recent library updates related > to font handling, so I tried back out to the previous version for > each. It turns out that when I reverted to version 1.7.4-1 of > libharfbuzz0, xwin-xdg-menu.exe stopped crashing. > > If it matters, both these systems are the Fall Creator's Update (1709) > of Windows 10 64-bit, and I'm running the 32-bit version of Cygwin. > > Hopefully someone can track down and fix this recent bug! > > Thanks, > Gilles > -- Gilles R. Detillieux E-mail: Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences, Univ. of Manitoba Winnipeg, MB R3E 0J9 (Canada) -- 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