Ruby on Rails
JavaScript, XHTML, CSS
Java, Distributed Systems
<you_name_it>
gettext
Memory Leaks in GetText for Ruby on Rails
Submitted by Steffen on Sat, 03/22/2008 - 09:30Version 1.90.0 of GetText for Ruby has quite some memory leaks in its Rails support files. In my case, the memory Mongrel used increased by 1 MB with each request it served... Quite amazing that you don't really find someone else having the problem... Well there's at least a bug report on rubyforge...
Monkey-patching gettext.rb with the following code made things quite more relaxed:
def bound_target(klass = self) # :nodoc:
ret = nil
Ruby on Rails: gettext + memcache = trouble
Submitted by Steffen on Sat, 09/29/2007 - 06:25The latest Ruby gettext 1.10.0 gem broke the memcache based fragment caching of the current project I'm working on. I figured out what the problem was. gettext 1.10.0 tries to localize caching of fragments by kind of appending the Locale.current to the fragment cache key, e.g. "items/show/1" becomes "items/show/1_en", "items/show/1_de", ...
This by itself isn't a problem but gettext also overwrites the default Rails implementation for expiring fragments. The gettext mechanism expires each localized cache fragment for a given key, e.g. "items/show/1_*" (where * is a wildcard). The current memcache-client gem (1.5.0) however doesn't support wildcard based key access and a "delete_if method not defined" exception gets thrown.
