Re: Segfault in vim-obsession

------=_Part_138410_1599167244.1781669697506
Content-Type: multipart/alternative; 
	boundary="----=_Part_138411_1283053052.1781669697506"

------=_Part_138411_1283053052.1781669697506
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

In the recent vim, session files were changed to be able to process=20
vim9script related mappings.

Might be related or not.

On Thursday, June 11, 2026 at 6:15:44=E2=80=AFPM UTC+10 Manas wrote:

> Hi folks, I probably should have posted this on
> [vim-obsession](https://github.com/tpope/vim-obsession) issue page, but I=
=20
> cannot
> reproduce it fully. I wanted to know if someone has seen this too.
>
> I have seen vim crash with a segfault twice now, after I installed and=20
> started
> using vim-obsession. Their issue page is empty about any segfaults. But I=
=20
> am
> quite positive that segfault crash only started occuring after=20
> vim-obsession
> managed my `Session.vim`. Previously, I was manually saving `Session.vim`=
=20
> and
> never saw any segfault.
>
> One more observation may involve tmux. I recall moving across tmux panes=
=20
> and
> sessions, and when I came back to the vim pane, I saw it crashed.
>
> Unfortunately, I don't know how to reproduce it.
>
> Thanks
> --=20
> Manas
>

--=20
--=20
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---=20
You received this message because you are subscribed to the Google Groups "=
vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/vim_use/ed6=
51fa0-c8e2-4430-b9b3-ff65aa8fa0dbn%40googlegroups.com.

------=_Part_138411_1283053052.1781669697506
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>In the recent vim, session files were changed to be able to process vi=
m9script related mappings.</div><div><br /></div><div>Might be related or n=
ot.</div><br /><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_=
attr">On Thursday, June 11, 2026 at 6:15:44=E2=80=AFPM UTC+10 Manas wrote:<=
br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; b=
order-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi folks, I p=
robably should have posted this on
<br>[vim-obsession](<a href=3D"https://github.com/tpope/vim-obsession" targ=
et=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://www.google.c=
om/url?hl=3Den&amp;q=3Dhttps://github.com/tpope/vim-obsession&amp;source=3D=
gmail&amp;ust=3D1781756004891000&amp;usg=3DAOvVaw2_LLYim9yi2JwQxuszpVrW">ht=
tps://github.com/tpope/vim-obsession</a>) issue page, but I cannot
<br>reproduce it fully. I wanted to know if someone has seen this too.
<br>
<br>I have seen vim crash with a segfault twice now, after I installed and =
started
<br>using vim-obsession. Their issue page is empty about any segfaults. But=
 I am
<br>quite positive that segfault crash only started occuring after vim-obse=
ssion
<br>managed my `Session.vim`. Previously, I was manually saving `Session.vi=
m` and
<br>never saw any segfault.
<br>
<br>One more observation may involve tmux. I recall moving across tmux pane=
s and
<br>sessions, and when I came back to the vim pane, I saw it crashed.
<br>
<br>Unfortunately, I don&#39;t know how to reproduce it.
<br>
<br>Thanks
<br>--=20
<br>Manas
<br></blockquote></div>

<p></p>

-- <br />
-- <br />
You received this message from the &quot;vim_use&quot; maillist.<br />
Do not top-post! Type your reply below the text you are replying to.<br />
For more information, visit <a href=3D"http://www.vim.org/maillist.php">htt=
p://www.vim.org/maillist.php</a><br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;vim_use&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">vim_use+uns=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
vim_use/ed651fa0-c8e2-4430-b9b3-ff65aa8fa0dbn%40googlegroups.com?utm_medium=
=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/vim_use/ed6=
51fa0-c8e2-4430-b9b3-ff65aa8fa0dbn%40googlegroups.com</a>.<br />

------=_Part_138411_1283053052.1781669697506--

------=_Part_138410_1599167244.1781669697506--