From: nagachika00@...
Date: 2015-05-19T19:54:23+00:00
Subject: [ruby-core:69245] [Ruby trunk - Bug #10942] Suspected memory leak

Issue #10942 has been updated by Tomoyuki Chikanaga.

Backport changed from 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: REQUIRED to 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONE

Backported into `ruby_2_2` branch at r50550.
I've changed :limit option for assert_no_memory_leak from 1.5 to 2.0. Without the change added test sometimes fails on my environment.

----------------------------------------
Bug #10942: Suspected memory leak
https://bugs.ruby-lang.org/issues/10942#change-52500

* Author: Johan Lundahl
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONE
----------------------------------------
There seems to be memory leaking when calling Aws::SQS::Client#receive_message in Ruby 2.2.0 and 2.2.1. I am not very good at memory/object allocation profiling in Ruby, but I know for sure that there must be some issue, because my SQS workers run out of memory every day.

See gist https://gist.github.com/quezacoatl/7657854f371edcb5d8e6 to reproduce. I've added output.txt for my output for different Ruby versions. Ruby 2.1.2 works fine. I'm sorry that I cannot pinpoint the exact issue. Perhaps somebody with better profiling skills can do this?

---Files--------------------------------
0001-stringio-avoid-STR_NOFREE-due-to-constant-string.patch (1.49 KB)


-- 
https://bugs.ruby-lang.org/