[vim/vim] Last buffer not freed with EXITFREE (PR #19194)

2 views
Skip to first unread message

zeertzjq

unread,
Jan 16, 2026, 5:49:00 PMJan 16
to vim/vim, Subscribed

Problem: Last buffer not freed with EXITFREE (after 9.1.2087).
Solution: Free the last buffer when inside free_all_mem().

This isn't really a memory leak, as the last buffer's memory is still
reachable via pointers like firstbuf and lastbuf. But it's possible that
this may cause false ASAN warnings in the future, which is what EXITFREE
is supposed to prevent.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19194

Commit Summary

  • 12f04b1 Last buffer not freed with EXITFREE

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19194@github.com>

zeertzjq

unread,
Jan 16, 2026, 5:50:49 PMJan 16
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • ae3b11f Last buffer not freed with EXITFREE


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19194/before/12f04b1756db513a4114ea0001b8f1f3d6890eab/after/ae3b11ffa1eda87993902bf92ed9eb29c0e8e489@github.com>

Christian Brabandt

unread,
Jan 17, 2026, 5:13:57 AMJan 17
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19194)

thanks


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19194/c3762989302@github.com>

Christian Brabandt

unread,
Jan 17, 2026, 5:15:58 AMJan 17
to vim/vim, Subscribed

Closed #19194 via 6c118af.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19194/issue_event/22111730952@github.com>

Reply all
Reply to author
Forward
0 new messages