From: rubybugsbmw@... Date: 2016-11-18T14:51:09+00:00 Subject: [ruby-core:78195] [Ruby trunk Bug#12954] valgrind shows memory leaks Issue #12954 has been reported by Bernhard M. Wiedemann. ---------------------------------------- Bug #12954: valgrind shows memory leaks https://bugs.ruby-lang.org/issues/12954 * Author: Bernhard M. Wiedemann * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.2.5p319 * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- I found that ruby itself is leaking plenty memory in ruby2.2, ruby2.1 and ruby1.9 The only version without such leakage was ruby1.8. Steps To Reproduce on openSUSE Tumbleweed: zypper mr -e repo-debug zypper in --no-recommends valgrind libruby2_2-2_2-debuginfo valgrind --log-file=/tmp/valgrind-ruby.txt --show-leak-kinds=definite \ --leak-check=full /usr/bin/ruby -e '' Actual Results: /tmp/valgrind-ruby.txt shows 820KB leaked: definitely lost: 223,845 bytes in 2,064 blocks indirectly lost: 599,241 bytes in 11,712 blocks It is less when running with --disable-gems but still existing. And when adding a 'require "chef"' line, it goes above 6MB leaked. -- https://bugs.ruby-lang.org/ Unsubscribe: