Run the following vim script. You will need to use Ctrl-C to stop it.
new
call prop_type_add('comment', {'highlight': 'Directory'})
call setline(1, ['one', 'two', ''])
let id_a = prop_add(1, 0, {'type': 'comment', 'text': '<text-a>'})
let id_b = prop_add(2, 0, {'type': 'comment', 'text': '<text-b>'})
let n = 0
while n < 10000
let k = 0
while k < 10000
call prop_remove({'type': 'comment'}, 1)
let id_a = prop_add(1, 0, {'type': 'comment', 'text': '<text-a>'})
call prop_remove({'type': 'comment'}, 2)
let id_b = prop_add(2, 0, {'type': 'comment', 'text': '<text-b>'})
let k += 1
endwhile
call setline(3, printf('id_a=%d id_b=%d', id_a, id_b))
let n += 1
sleep 10m
redraw
endwhile
The memory use should be stable, but memory use increases over time.
Note that the underlying data structure in Vim increases by doubling in size,
so over time jumps in memory use become less frequent, but larger.
The above example is contrived, but perfectly legitimate plug-in code could
cause this. I suspect I have seen this occurring while investigating a different
issue.
9.2.112
OS = LinuxMint 21.1
terminal = Terminator /
$TERM = xterm-256color
shell = Xonsh / Bash
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()