[ruby-core:94317] [Ruby master Bug#11459] Ruby leaks several MB of memory every setup/eval/cleanup cycle.
From:
merch-redmine@...
Date:
2019-08-13 04:16:07 UTC
List:
ruby-core #94317
Issue #11459 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Open to Closed `ruby_cleanup` should only be called once per process, before exiting (either via `main`->`ruby_run_node` or `ruby_stop`). It is not expected to free all memory allocated earlier, since the process will be exiting and the operating system should free the remaining memory. ---------------------------------------- Bug #11459: Ruby leaks several MB of memory every setup/eval/cleanup cycle. https://bugs.ruby-lang.org/issues/11459#change-80679 * Author: scorpion007 (Alex Budovski) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: latest master * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- Even with a trivial eval "1" Ruby leaks about 2 MB or so after ruby_cleanup. I've attached the raw list of leaks as reported by the CRT (I took a snapshot before ruby_setup and again after ruby_cleanup). I've also attacked a few sample callstacks of the leaks (I picked 5 or so randomly). Isn't ruby_cleanup supposed to clean something up? ---Files-------------------------------- rubyleaks.txt (1.47 MB) ruby_leak_stacks.txt (8.4 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>