Subject: Re: bug#70914: 29.3; Crashes often on Windows

From: Eli Zaretskii <[email-masked]>
Date: Wed, 22 May 2024 17:03:19 +0300

> From: Simen Endsjø <[email-masked]>
> Date: Wed, 22 May 2024 15:14:33 +0200
> Cc: Hannes Domani <[email-masked]>, [email-masked], [email-masked]
> 
> Lisp Backtrace:
> "file-exists-p" (0xbf7ec0)
> "or" (0xbf80d0)
> "if" (0xbf8280)
> 0xd337f40 Lisp type 3
> "org-activate-links--overlays" (0x4a15a80)
> "org-activate-links" (0x4a159f8)
> "font-lock-fontify-keywords-region" (0x4a15958)
> "font-lock-default-fontify-region" (0x4a158e8)
> "font-lock-fontify-region" (0x4a15890)
> "font-lock-default-fontify-buffer" (0x4a15848)
> "font-lock-fontify-buffer" (0x4a157f8)
> "org-fancy-priorities-mode" (0xbf8b58)
> "run-hooks" (0xbf8d28)
> "apply" (0x4a157b8)
> "run-mode-hooks" (0x4a15758)
> "org-mode" (0x4a15718)
> "set-auto-mode-0" (0x4a156c8)
> "set-auto-mode--apply-alist" (0x4a15648)
> 0x3f35f40 PVEC_COMPILED
> "apply" (0x4a155d8)
> 0x615ebd0 PVEC_COMPILED
> "apply" (0xbf9d50)
> "progn" (0xbf9fb0)
> "unwind-protect" (0xbfa150)
> "let" (0xbfa3e0)
> "evil-save-state" (0xbfa540)
> "if" (0xbfa6f0)
> "+evil--persist-state-a" (0x4a15598)
> "apply" (0x4a15590)
> 0xa983000 PVEC_COMPILED
> "apply" (0x4a15550)
> "so-long--set-auto-mode" (0x4a15508)
> "apply" (0x4a15500)
> "set-auto-mode" (0x4a154b8)
> "normal-mode" (0x4a15468)
> 0x3f22060 PVEC_COMPILED
> "apply" (0xbfc0d0)
> "progn" (0xbfc330)
> "unwind-protect" (0xbfc4d0)
> "let*" (0xbfc710)
> "doom--shut-up-autosave-a" (0xbfc938)
> "apply" (0x4a15400)
> 0xa6eaab0 PVEC_COMPILED
> "apply" (0x4a153c0)
> 0xa6eab10 PVEC_COMPILED
> "apply" (0x4a15380)
> "after-find-file" (0x4a15338)
> "find-file-noselect-1" (0x4a152a0)
> "find-file-noselect" (0x4a15210)
> "find-file" (0x4a15168)
> 0x1d009250 PVEC_COMPILED
> "apply" (0x4a15130)
> "consult-recent-file" (0xbfeae0)
> "funcall-interactively" (0xbfead8)
> "call-interactively" (0x4a150a0)
> "command-execute" (0xbff408)

Thanks.  Too much is involved here, but my money is on consult: I see
in its code several places where it matches file names in a way that
can only work on Posix systems (i.e., assuming absolute file names
begin with a slash, not with a drive letter).  Since
consult-recent-file is in the Lisp backtrace, it's a definite
possibility.

Another possibility is that some of your customizations includes such
a file name.

Anyway, now at least that crash shouldn't happen anymore.

You can now remove the added condition and the call to emacs_abort
from the code.  Please run for a while and see if there are any other
crashes like that one, which yield a zero code address.