Issue #13783 has been updated by opti (Andreas Opti).


I didn't manage to compile v250 (because of other errrors), nice to see that this bug is fixed now.
(mentioned it in a mailinglist sometimes ago).
Now I found "r59074 | ko1 | 2017-06-13 11:52:33 +0900 (Tue, 13 Jun 2017) | 5 lines" in the changelog,
maybe s.o. could backported that to 2.4.x ?
Seems also if updating 2.4.x -> 2.4.x+1 I have to reinstall [compile] all gems?

thanks
Opti


----------------------------------------
Bug #13783: Memory allocation / GC does not free unused memory
https://bugs.ruby-lang.org/issues/13783#change-66051

* Author: opti (Andreas Opti)
* Status: Feedback
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
100.times {x=[]; 1000000.times {|i| x.push [i,i*3]} }
100.times should use (more or less) the same memory as 3.times, 
also GC.start after x=[] doesn't help!
Problem: system begins swapping if doing that many times (using large data arrays running for longer times)




-- 
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>