From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org (ruby-talk ML) ,rainbows-talk@rubyforge.org
Subject: [ANN] Rainbows! 0.90.2 - leak fix from Unicorn
Date: Sat, 13 Feb 2010 19:37:59 +0900 [thread overview]
Message-ID: <20100213103757.GB7833@dcvr.yhbt.net> (raw)
In-Reply-To: <20100213103409.GA7833@dcvr.yhbt.net>
This release depends on Unicorn 0.96.1 for an updated
Unicorn::HttpParser to avoid leaking memory.
The HttpParser in Unicorn <= 0.96.0 did not setup the parser
object properly to be freed by the garbage collector.
While this bug did not affect Unicorn itself, Rainbows!
allocates a new Unicorn::HttpParser object for every new client
connection and Unicorn did not properly setup the parser object
to be freed by the Ruby garbage collector.
There are also minor cosmetic cleanups and fixes:
Eric Wong (10):
http_response: disallow blank, multi-value headers
Fix "rainbows -h" and "rainbows -v"
Update docs + tests to reflect Rev 0.3.2 release
local.mk.sample: bump Rack dependency
Merge branch 'rack-1.1'
add Cramp integration tests
Rakefile: autoload Gem
t/bin/*: encoding should be the first line after shebang
gemspec: bump dependency on Unicorn to avoid leak
Rainbows! 0.90.2
* http://rainbows.rubyforge.org/
* rainbows-talk@rubyforge.org
* git://git.bogomips.org/rainbows.git
--
Eric Wong
next prev parent reply other threads:[~2010-02-13 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 10:34 [ANN] unicorn 0.96.1 - leak fix for Rainbows!/Zbatery Eric Wong
2010-02-13 10:37 ` Eric Wong [this message]
[not found] ` <20100213103757.GB7833-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2010-02-13 10:39 ` [ANN] Zbatery 0.1.1 - leak fix from Unicorn Eric Wong
2010-03-01 18:55 ` [ANN] Rainbows! 0.91.0 - Unicorn resync Eric Wong
2010-03-01 18:58 ` [ANN] Zbatery 0.2.0 - Unicorn/Rainbows! resync Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/rainbows/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100213103757.GB7833@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=rainbows-talk@rubyforge.org \
--cc=ruby-talk@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/rainbows.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).