From: Michael Albinus <michael.albinus@gmx.de>
To: Mani Kancherla <kancherla.mani@gmail.com>
Cc: 50205@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#50205: 27.2; crashes or hangs when opening a specific file using tramp
Date: Thu, 09 Sep 2021 09:02:26 +0200 [thread overview]
Message-ID: <87y2869qpp.fsf@gmx.de> (raw)
In-Reply-To: <CAGaWTtAW0ajRx4GzUt3QPOR2Vqayn3FGPJaYhCb1F=h_0mBEfw@mail.gmail.com> (Mani Kancherla's message of "Wed, 8 Sep 2021 14:12:27 -0700")
Mani Kancherla <kancherla.mani@gmail.com> writes:
> Hi Michael,
Hi Mani,
> Sorry, it took me some time to get back to you. I asked one of my
> colleagues to try it on her MAC.
> We installed emacs 27.2 on that MAC first and then tramp 2.5.1,
> verified that tramp 2.5.1 is loaded
> with M-x tramp-version and then we could easily reproduce the issue.
>
> I also suspect that it is related to tramp on MAC. I had been using
> emacs and tramp for a few years
> without trouble and I think the issues started last year. I don't
> remember if it was after I upgraded my
> MAC to the latest version at that time.
>
> What I noticed is that, occasionally, sometimes within an hour and
> sometimes after a couple of days, emacs
> crashes. I tried upgrading MAC OS, emacs, tramp and nothing helped.
> Then I tried to narrow it down
> so I could consistently reproduce it.
>
> Switching to the built-in 2.4.5.27.2 helped, i.e. reduced the
> frequency of crashes significantly and also I
> don't see the issue with the specific file that I could reproduce the
> issue with consistently. However, I still see
> emacs crashing occasionally. I am trying to run it in debugger and see
> if I can gather useful info.
All of this requires macOS specific debugging. I've added Alan in Cc, he
has fixed some macOS specific crashes. Perhaps, he has an idea.
> Thanks,
> Mani
Best regards, Michael.
next prev parent reply other threads:[~2021-09-09 7:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:24 bug#50205: 27.2; crashes or hangs when opening a specific file using tramp Mani Kancherla
2021-08-26 6:26 ` Eli Zaretskii
[not found] ` <CAGaWTtCxKX8=qavjiubFrnMcQShBax86OM7SAeTmnHEmd6z-qA@mail.gmail.com>
2021-08-27 6:04 ` Eli Zaretskii
2021-08-27 6:51 ` Michael Albinus
2021-08-27 20:37 ` Mani Kancherla
2021-08-27 21:14 ` Mani Kancherla
2021-08-28 8:13 ` Michael Albinus
2021-08-28 21:26 ` Mani Kancherla
2021-08-29 7:23 ` Michael Albinus
2021-08-30 20:50 ` Mani Kancherla
2021-09-02 7:22 ` Michael Albinus
2021-09-03 16:44 ` Mani Kancherla
2021-09-04 7:06 ` Michael Albinus
2021-09-08 21:12 ` Mani Kancherla
2021-09-09 7:02 ` Michael Albinus [this message]
2021-09-09 16:41 ` Alan Third
2021-09-11 0:20 ` Mani Kancherla
2021-09-11 8:06 ` Michael Albinus
2021-09-15 0:55 ` Mani Kancherla
2021-09-15 6:52 ` Alan Third
2021-09-17 21:01 ` Mani Kancherla
2021-09-18 7:07 ` Michael Albinus
2021-09-18 7:52 ` Michael Albinus
2021-09-24 20:39 ` Mani Kancherla
2021-10-05 16:40 ` Mani Kancherla
2021-10-06 7:18 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2869qpp.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=50205@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=kancherla.mani@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).