vimr
vimr copied to clipboard
qvacua
A memory leak was encountered while editing a [new] vim document
Hello, I was using Version 0.32.0 (344) and I encountered a memory leak of several gigabytes when editing a piece of text with around 4000 characters, 669 words, and 129 lines. The text was not written to a file yet - it was just in the vimr program without being saved to disk anywhere.
The text itself was myself switching back and forth between a YouTube video I was transcribing and the text editor over the course of 10-20 minutes.
I had to force quit vimr to stop my machine from running out of memory. What can I do the next time or provide with you now to debug this problem?
Here is the original text I started with and here is close to what I ended up before I quit.
[update]
I encounter this bug even if I have no documents open at all as well.
Here's a YouTube video of the bug.
Here's a dump from Mac OS's Activity Monitor. vimr_debug_activity_monitor_sample.txt
This sounds a lot like an issue I'm observing too... After having VimR running for a while, my machine gets quite sluggish, and every time it's VimR eathing 3-4GB of memory.
Is there anything I can do to help out diagnose this?
Trying not to just be a +1 here, but there is definitely a memory leak in some unexpected circumstances with the most recent release. I had an empty vimr running, just a blank initial buffer, nothing open no text nothing and came back to my computer in the morning with an OSX popup that I should select what to kill due to OOM conditions. The vimr application was being accounted 248GB of virtual memory and had actually touched enough of it to cause the oom killer to start and kill most other applications on my computer.
Just letting a copy sit around and watching the memory (frustratingly instruments refuses to attach to anything on this laptop or I would include a trace, sorry) it hovers around 85MB for a while but periodically grows in small increments over time. Due to the darned notarized binary debugging restriction I can't do much better than that without building locally, but something is definitely going on here.
