From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id B06A91F406 for ; Fri, 11 May 2018 05:43:41 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 61BF5120972; Fri, 11 May 2018 14:43:38 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id 515B0120938 for ; Fri, 11 May 2018 14:43:33 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 39C3B1F406; Fri, 11 May 2018 05:43:31 +0000 (UTC) Date: Fri, 11 May 2018 05:43:30 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20180511054330.GA27091@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 86988 Subject: [ruby-core:86988] Re: [Ruby trunk Bug#14745] High memory usage when using String#replace with IO.copy_stream X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" janko.marohnic@gmail.com wrote: > def initialize(content) > @io = StringIO.new(content) > end > > def read(length, outbuf) > chunk = @io.read(length) Finally, I always assumed your example is a contrived case and you're dealing with an interface somewhere (not StringIO) which doesn't accept a destination buffer for .read. Fwiw, I encountered a similar problem with Net::HTTP and Zlib::GzipReader earlier this year and made r61665 to ensure outbuf got used all the way down the call chain. Sometimes I guess modifying/fixing interfaces is the only way to go. (unless we can do escape analysis, but I'm not sure how feasible it is with a dynamic language)