[ruby-core:78237] Re: [Ruby trunk Bug#12954][Feedback] valgrind shows memory leaks
From:
Eric Wong <normalperson@...>
Date:
2016-11-21 19:51:35 UTC
List:
ruby-core #78237
nobu@ruby-lang.org wrote:
> It's intentional that many objects (classes, methods, etc) are not freed.
> Probably it's better to tell valgrind not to report such things.
> Patches are welcome.
100% agreed, valgrind suppression files are preferred.
free() calls are slow, it is typical for free() to be slower
than {m,c,re}alloc() functions); this slows down the runtime
of short-lived scripts.
In fact, I've wanted to disable memory release during VM exit to
speed up short-lived scripts, but haven't gotten around to it...
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>