From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Aaron Jensen Newsgroups: gmane.emacs.bugs Subject: bug#30800: 26.0.91; unknown crash on macos Date: Thu, 22 Mar 2018 08:39:32 -0700 Message-ID: References: <83muz1jrdv.fsf@gnu.org> <83k1u5jqxm.fsf@gnu.org> <83in9pjnkc.fsf@gnu.org> <83fu4tjmdv.fsf@gnu.org> <20180321191903.GA38993@breton.holly.idiocy.org> <83d0zxjk5p.fsf@gnu.org> <20180321201234.GA39094@breton.holly.idiocy.org> <834ll8k1tx.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1521733097 31478 195.159.176.226 (22 Mar 2018 15:38:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Mar 2018 15:38:17 +0000 (UTC) Cc: Alan Third , 30800@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 22 16:38:12 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ez2I7-00085j-J2 for geb-bug-gnu-emacs@m.gmane.org; Thu, 22 Mar 2018 16:38:11 +0100 Original-Received: from localhost ([::1]:33245 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ez2K9-0008JK-65 for geb-bug-gnu-emacs@m.gmane.org; Thu, 22 Mar 2018 11:40:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35283) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ez2Jy-0008DU-U1 for bug-gnu-emacs@gnu.org; Thu, 22 Mar 2018 11:40:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ez2Ju-0008MA-WD for bug-gnu-emacs@gnu.org; Thu, 22 Mar 2018 11:40:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:40132) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ez2Ju-0008LU-SJ for bug-gnu-emacs@gnu.org; Thu, 22 Mar 2018 11:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ez2Ju-0004j3-Fs for bug-gnu-emacs@gnu.org; Thu, 22 Mar 2018 11:40:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Aaron Jensen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 22 Mar 2018 15:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30800 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30800-submit@debbugs.gnu.org id=B30800.152173318118132 (code B ref 30800); Thu, 22 Mar 2018 15:40:02 +0000 Original-Received: (at 30800) by debbugs.gnu.org; 22 Mar 2018 15:39:41 +0000 Original-Received: from localhost ([127.0.0.1]:48029 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ez2JY-0004iN-OK for submit@debbugs.gnu.org; Thu, 22 Mar 2018 11:39:40 -0400 Original-Received: from mail-qk0-f172.google.com ([209.85.220.172]:32902) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ez2JW-0004iB-TW for 30800@debbugs.gnu.org; Thu, 22 Mar 2018 11:39:39 -0400 Original-Received: by mail-qk0-f172.google.com with SMTP id k66so1887162qkc.0 for <30800@debbugs.gnu.org>; Thu, 22 Mar 2018 08:39:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HPWU7wPSp5c44DsGTg8p7c3fgv/Qisy+iNYuXdmsjmI=; b=AeBzdfft0nUAsmvxduZprBeVtFgQeRx06RZKryOCarvgCJLks+zW0YD9r51lZ9QtW5 p4De57hw80nAi9rXIo6BZ9WjDVqqpgoNZhgEQar31y/5LokGsoMAKqwb7sDjg/BKy1zp RcMgXjArTotornlCf1RJRfAgMQnw+jrlwphAqs0IXkhMxfDxJc8UQJhk7K/MceMlZjif cljuLe46UmrQwA5bEFgAsZVeoFpLQfvxRNHUKOeM+7rnGL/gntlbGQKBh4l/y8PdQDdK +d0w1xmB6lPexqnBJQpivCtoBgorRKG8h+Q4BnqVlm+2xHvYrwIwaUhY5oHxqh55eLrm Pd2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HPWU7wPSp5c44DsGTg8p7c3fgv/Qisy+iNYuXdmsjmI=; b=APJmWHFDXnkp7AiSRjIrwvXRB67AxFH+PbX5HssHP9ObL7VeD+T0ZB50RvuBHjZknM KWsbnp4GJSfsTY4vJC9IHVv2KJR5SZpne/qGBi4rFmqWL0pH6iK8XeojpkA/usYV47pj xTqvR7M7zeVI0uyAvMR3WFKbhf9RxESQ2Q3PwIcci/E7BW15yXk4hl1xvkpGrvBrxNop gMST1eKI4tOqC46/JA8P6n3eXn/Swo/QxpEMAaVMC2ZJlL6dx1tFAIy8GWlFl7A2xnVz fsqLEms6uOdmaZRALJCReprZTJnCF6Ys6TjmpEWGcuIXCPL4j5yAlBAvdziXdJzKOd1O bcbA== X-Gm-Message-State: AElRT7H1RAYvtxR40iSG4YtzDA0OlFGCIMhEkDm0JvZCiCZocZxO9Y+l sczK3gO7nulSvtbvi9VbHrZMaMo92ZDe6WeERtU= X-Google-Smtp-Source: AG47ELtVhW56hPiZQtwV6pa9KTzGCmXFMfH93nA2J04DOW7Wzm2M5A7J/6zeUmCEY3oOQenOd14iMxDJWtdmJJwU2FU= X-Received: by 10.55.162.66 with SMTP id l63mr11021826qke.124.1521733173231; Thu, 22 Mar 2018 08:39:33 -0700 (PDT) Original-Received: by 10.237.60.76 with HTTP; Thu, 22 Mar 2018 08:39:32 -0700 (PDT) In-Reply-To: <834ll8k1tx.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:144528 Archived-At: On Thu, Mar 22, 2018 at 12:26 AM, Eli Zaretskii wrote: >> I do not understand why setting the represented filename where it was >> set originally causes a flicker. > > I don't understand, either, especially since I don't see this on w32. > > The recipes in bug#18757 seem to indicate that redisplaying the > frame's title, due to the change in the selected buffer, causes the > flickering. That flickering started happening with the upgrade to > version 10.10 of the OS, so perhaps it's no linger an issue with the > current OS versions? > >> It's probably a dumb question, but would using the start/stop paint >> stuff from the flicker bug help to eliminate the flicker in some way? > > Do you still see the flicker if you revert the above commit? I do not on 10.13.2 when I follow the steps outlined in the original report. I don't know what's going on in the code exactly, but would it be worth it to risk the flicker on older macOS (or people's setups that can repro it if mine just can't) in order to ensure that the represented filename gets set on a frame that is about to be freed? Or maybe there's something more that's going on here that I don't understand. By the way, flycheck-posframe changed it so that they hide the frame (and eventually reuse it) instead of killing it after it is used, which should make this crash less likely in the future for others. I still think it should be patched, but that's some good news. Related to that, the more consistent repro for this is to use flycheck-posframe and move the point to and from an error, which causes the a new frame to flicker in and out of existence. It's probably possible to script this to an even more concise repro.