[ruby-core:78230] Re: [Ruby trunk Bug#12954] valgrind shows memory leaks
From:
Kirk Haines <wyhaines@...>
Date:
2016-11-20 17:03:59 UTC
List:
ruby-core #78230
On Sat, Nov 19, 2016 at 10:47 AM, <[email protected]> wrote: > Issue #12954 has been updated by Robert A. Heiler. > > > I am not sure how easy it is for the ruby core team to reproduce it. > It isn't difficult to reproduce it, but I'm not convinced that it's a real memory leak. I've just been looking at it for a few minutes, and it feels like it's a bookkeeping issue when Ruby is taking down the VM and freeing everything in the object space. Specifically, my hunch is that classes which are defined via C have memory which isn't being cleaned up properly on vm exit, resulting in valgrind reporting a memory leak. I will look at it in more detail later today and see if I can specifically confirm my hunch. Kirk Haines Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>