[typo] [FATAL] failed to allocate memory
steve.longdo at gmail.com
Tue Aug 15 14:46:08 EDT 2006
This is very similar to what I use. Mostly because doing anything better
becomes an exercise in a C extension to hook into the Ruby interpreter.
Seems like a C heap walker would be smart enough to use for this purpose.
Maybe when Apple adds RoR they will make XCode able to profile Ruby on OS
On 8/15/06, Paul Brown <paulrbrown at gmail.com> wrote:
> On 8/15/06, Scott Laird <scott at sigkill.org> wrote:
> > One thing I'd recommend (if you aren't doing this already) is to build
> > a memory profiler component with an action that dumps your memory
> > profile data. Then you can run zillions of queries without paying the
> > price of the memory profiler per hit, while still having your data
> > always be accessible.
> > If one of these was easily available, then I wouldn't have to write my
> > own when I start working on memory leaks. Hint, hint.
> Heh. You can get away with something simpler. Do what I did:
> 1) Add the profile hook as an after filter on the main article controller.
> 2) Add a class-level variable (@@next_time_to_run).
> 3) Set an interval at which to run the profile dump.
> Links to profiling code snippet, etc., are here:
> paulrbrown at gmail.com
> Typo-list mailing list
> Typo-list at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Typo-list