From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Simen =?UTF-8?Q?Endsj=C3=B8?= Newsgroups: gmane.emacs.bugs Subject: bug#70914: 29.3; Crashes often on Windows Date: Thu, 16 May 2024 12:50:06 +0200 Message-ID: References: <86msouxamh.fsf@gnu.org> <86h6f0wsbv.fsf@gnu.org> <86seyjtgvd.fsf@gnu.org> <86ttizjdwm.fsf@gnu.org> <86h6eykiuk.fsf@gnu.org> <86cypmji2l.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23558"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 70914@debbugs.gnu.org, Corwin Brust To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 16 12:52:25 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s7Yin-0005sh-D3 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 16 May 2024 12:52:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s7YiR-0007pn-9Y; Thu, 16 May 2024 06:52:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7YiO-0007pJ-Eq for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 06:52:01 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s7YiO-0005aw-0L for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 06:52:00 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s7YiQ-0001om-5f for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 06:52:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Simen =?UTF-8?Q?Endsj=C3=B8?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 16 May 2024 10:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70914 X-GNU-PR-Package: emacs Original-Received: via spool by 70914-submit@debbugs.gnu.org id=B70914.17158566906965 (code B ref 70914); Thu, 16 May 2024 10:52:02 +0000 Original-Received: (at 70914) by debbugs.gnu.org; 16 May 2024 10:51:30 +0000 Original-Received: from localhost ([127.0.0.1]:48071 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7Yht-0001oH-QJ for submit@debbugs.gnu.org; Thu, 16 May 2024 06:51:30 -0400 Original-Received: from mail-lf1-f43.google.com ([209.85.167.43]:61608) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7Yhq-0001oB-TP for 70914@debbugs.gnu.org; Thu, 16 May 2024 06:51:28 -0400 Original-Received: by mail-lf1-f43.google.com with SMTP id 2adb3069b0e04-5231efd80f2so693407e87.2 for <70914@debbugs.gnu.org>; Thu, 16 May 2024 03:51:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715856618; x=1716461418; darn=debbugs.gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Jhbv39MwWq+buIMSg7i7vX26O/DOA9oKwnFS528qJro=; b=JnGQUMo3AWqynsQfbyLbnHnol2wVZfQaBwLpFhY7oVxMjAVn6avGDUqX3ZJskPVD5O NXKESgl1u6SOmtoyrVxyUtGFlT2rbXZco72k2JHyDnNuBryn53b2kfRNBCbPMvR3qvwS 3xYxZ5N3tDuDWKNn0mYG3/BYMvhelcvNZ/MiT8Aq9moROyuc6Y2uHm4TZItLQI9gWQdy bgf9hePOl52NteCEdaG1i+wGjOU51dKlqdxz5v4ddZWiB8tQWlt6/aaJpD+bZwcnn52z p2J0iWk79wkXHmO1Ji/QHupz4oitum4RB4WvjeBsvGOaWfQEaj76Gq0DGtBVnw4bgnKb 1VCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715856618; x=1716461418; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Jhbv39MwWq+buIMSg7i7vX26O/DOA9oKwnFS528qJro=; b=guIwVf7hrrPDx4TmqHj1XPpW4DmziFSE5c/LAsxFMAOpC38aRCXveLN7tnK4yRXs+7 CuSPGOXv02+tqSmitA747UDaYJzR5aicrEYNHgk+LeZDA8nasL8Vp/TH12My/WcVUagR tSTW/4m2e7CGE+nO1CnnJwq2bx7zdTBTiaP5dQGoO0hXnnX7sF2UvT3rEkWPa2Jrlzjw +9D63eI3JeWqnfu96yAmoSdLwY9hHwjJ4WBgPHSesbMQDCslSZbdvEuk3NchaTA3hRkd hOnJBsm0uG8tcNKr3WrbgThj3CZK6ErUyXogGl8pBxtTFAe7e0xzVLzFm7PZzStLZM3e cZpQ== X-Forwarded-Encrypted: i=1; AJvYcCX4xPKYR547WhEpiUNraF9Q9Ue/AMW7OzWsBYBikMQWedBPdCrAhssFNJYyL1yxKUdJqOYSQANBUHcgdZwt9b1OP00pUJY= X-Gm-Message-State: AOJu0YzIsEx+HpYvoPEh5+7K3NCTvM9bH1SqimmsAACdtSyK1lrGutU9 fUSmmdNF8nv5ABi4NoMQTQaSu7AXd6VNDVYQ2lc4Vhdbj18dxQkJTn7xYIbSaViK8/MSk2LNEtu CSMMlR2DxHQnNXfHjCBhn6WYgf+wXESaUknw= X-Google-Smtp-Source: AGHT+IG2q1Hw+YhP4QMnMsfNDnz87+HEKufVN4HZLWuT1IeuH0R1GRYdtENArys2iy98Us3B09zTU8m0iSKxiM1frAo= X-Received: by 2002:a05:6512:3ca4:b0:51d:67a0:2433 with SMTP id 2adb3069b0e04-52210074979mr14875716e87.46.1715856618169; Thu, 16 May 2024 03:50:18 -0700 (PDT) In-Reply-To: <86cypmji2l.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:285146 Archived-At: > Does this happen in "emacs -Q", or only with your customizations? If > the latter, perhaps try disabling the customizations one by one or in > related groups, so we could at least have some hint what triggers > these problems if not causes them. I think I managed to narrow it down, but I'm not exactly sure what combinat= ion of settings has to be in effect for it to trigger. We got an indication that there was a unicode problem earier, and as it cra= shes in org-mode buffers, I looked at the configuration there. When I turned of = the +pretty feature in Doom Emacs, it didn't crash anymore. (when (modulep! +pretty) (package! org-appear :pin "81eba5d7a5b74cdb1bad091d85667e836f16b997") (package! org-superstar :pin "54c81c27dde2a6dc461bb064e79a8b2089093a2= e") (package! org-fancy-priorities :pin "7f677c6c14ecf05eab8e0efbfe7f1b00ae68eb1d")) (after! org (setq org-highlight-latex-and-related '(native script entities))) (use-package! org-fancy-priorities ; priority icons :hook (org-mode . org-fancy-priorities-mode) :hook (org-agenda-mode . org-fancy-priorities-mode) :config (setq org-fancy-priorities-list '("=E2=9A=91" "=E2=AC=86" "= =E2=96=A0"))) (use-package! org-superstar ; "prettier" bullets :hook (org-mode . org-superstar-mode) :config ;; Make leading stars truly invisible, by rendering them as spaces! (setq org-superstar-leading-bullet ?\s org-superstar-leading-fallback ?\s org-hide-leading-stars nil org-superstar-todo-bullet-alist '(("TODO" . 9744) ("[ ]" . 9744) ("DONE" . 9745) ("[X]" . 9745)))) (use-package! org-appear ; better markup edit :hook (org-mode . org-appear-mode)) When looking ath the org-superstar-mode documentation I see the following section The package in question has matured, but suffers from intricate timing errors which will require looking into. Especially since they are so fa= r impossible to test reliably due to their nature. Ref https://github.com/integral-dw/org-superstar-mode?tab=3Dreadme-ov-file#= planned-features I cannot see any open or closed issues referring to crashes though. But this might indicate why I'm not getting the errors reproducible, and th= at I get them a lot when debugging. Looks like I need both org-superstar and org-fancy-priorities for it to tri= gger often. On Thu, May 16, 2024 at 10:07=E2=80=AFAM Eli Zaretskii wrote= : > > > From: Simen Endsj=C3=B8 > > Date: Wed, 15 May 2024 22:03:42 +0200 > > Cc: 70914@debbugs.gnu.org > > > > >> (process:13240): GLib-GIO-WARNING **: 20:15:06.678: Unexpectedly= , > > >> UWP app `Microsoft.OutlookForWindows_1.2023.1101.300_x64__8wekyb3d8b= bwe' > > >> (AUMId `Microsoft.OutlookForWindows_8wekyb3d8bbwe!Microsoft.Outlookf= orWindows') > > >> supports 1 extensions but has no verbs > > > > > > What are these warnings from Glib, and why should Emacs care about > > > problems with Outlook? > > > > After querying chatgpt a bit, it looks like GIO scans all installed app= lications > > on the systems, and shows warning for incorrectly specified ones: > > > > The warnings you're seeing indicate that certain UWP applications d= eclare > > extensions (indicating they have certain capabilities) but do not d= eclare > > any verbs (actions they can perform). This is unusual because typic= ally, an > > app that supports an extension should also support verbs to interac= t with > > those extensions. > > > > And that these are unrelated to the running process. > > Yes, I know all that already. I just don't understand why we see this > in Emacs from Glib, nor why should Glib make Emacs "scan all the > installed applications" in the first place. We only use Glib in Emacs > on Windows because it's a dependency of librsvg, so the above sounds > like some gross mis-configuration issue of librsvg as provided by the > MSYS2 folks. Corwin, any ideas about this? should we raise this issue > with the MSYS2 folks? > > > > I again suggest to review all the software installed there, maybe som= ething will > > > stand out. > > > > There is a lot of processes running on Windows, and I have no idea what= most > > is... Here's a list of the running processes. I've removed the command = line in > > case there's something sensitive there though. > > I didn't mean to look at the processes, I meant to look at the > installed software. Start Settings, then select System->System > Components, then review the installed Components. Then click on > "Installed apps" and review the applications you have installed. > > You can also do the last part with the "winget list" command from the > command line. > > For example, I see indications that you have Power Toys installed. So > maybe disable them (or uninstall completely, if you can), and see if > that helps. And maybe if you look at the installed components and > apps, there would be other clues like that. > > > Here's a new crash report using cmd.exe. Note that it didn't crash the = first > > time, so I `(kill-emacs)` and ran again to get a crash. > > Thanks. This again shows that the program counter got set to zero > somehow. Why that happens, I don't know. Perhaps some stack > overwriting, or some software that injects code into the running Emacs > process. > > Does this happen in "emacs -Q", or only with your customizations? If > the latter, perhaps try disabling the customizations one by one or in > related groups, so we could at least have some hint what triggers > these problems if not causes them. > > The only other idea I have is to try installing older versions of > Emacs -- if you find one that doesn't crash, maybe we could consider > the changes between it and the first version which does crash, and > take it from there (although the list of changes is usually huge, so > it won't be easy).