# Leak tracking x64

**URL:** <https://www.ruby-forum.com/t/leak-tracking-x64/192440>\
**Category:** Ruby\
**Created:** [July 30, 2010, 11:55am UTC](https://www.ruby-forum.com/t/leak-tracking-x64/192440 "2010-07-30T11:55:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Spurtus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/eada6e/32.png) [@Spurtus](https://www.ruby-forum.com/u/Spurtus)\
**Post date:** [July 30, 2010, 11:55am UTC](https://www.ruby-forum.com/t/leak-tracking-x64/192440/1 "2010-07-30T11:55:44Z")

</div>

Have easily reproducable memory leaks, need to find them.

I’m running Ruby 1.8.6 on an windows7 x64 machine.

I checked out memprof, bleak\_house et al. I can’t find anything  
compatible with my architecture / ruby version and prefer not to patch  
VM.

would it be worthwhile trying to walk the GC or is there some gem /  
tool or technique that I should be aware of?

Cheers,  
Spurtus.

---

<div class="post-metadata">

**Author:** ![Spurtus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/eada6e/32.png) [@Spurtus](https://www.ruby-forum.com/u/Spurtus)\
**Post date:** [July 30, 2010, 1:56pm UTC](https://www.ruby-forum.com/t/leak-tracking-x64/192440/2 "2010-07-30T13:56:26Z")

</div>

Spurtus wrote:

> Have easily reproducable memory leaks, need to find them.
> 
> I’m running Ruby 1.8.6 on an windows7 x64 machine.
> 
> I checked out memprof, bleak\_house et al. I can’t find anything  
> compatible with my architecture / ruby version and prefer not to patch  
> VM.

The only one I’m actually aware of (except perhaps Ruby based  
implementations like Dike gem) is  
[Software Tools | Software Verify](http://www.softwareverify.com/ruby/memory/index.html).

You might also get some traction from using jruby-esque tools.

[http://blog.headius.com/2010/07/browsing-memory-with-ruby-and-jdi.html](http://blog.headius.com/2010/07/browsing-memory-with-ruby-and-jdi.html)

Post back with your results.  
-r

---

<div class="post-metadata">

**Author:** ![Spurtus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/eada6e/32.png) [@Spurtus](https://www.ruby-forum.com/u/Spurtus)\
**Post date:** [August 4, 2010, 6:55am UTC](https://www.ruby-forum.com/t/leak-tracking-x64/192440/3 "2010-08-04T06:55:25Z")

</div>

On Fri, Jul 30, 2010 at 6:56 AM, Roger P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> You might also get some traction from using jruby-esque tools.
> 
> [http://blog.headius.com/2010/07/browsing-memory-with-ruby-and-jdi.html](http://blog.headius.com/2010/07/browsing-memory-with-ruby-and-jdi.html)
> 
> Post back with your results.

I would second the JRuby option. If it’s a library problem and the  
app/libraries all work under JRuby (they should unless they use things  
we don’t/can’t support), using JRuby to search for leaks is a great  
option.

Also see the first two posts in that series:

> **[Browsing Memory the JRuby Way](http://blog.headius.com/2010/07/browsing-memory-jruby-way.html)**
>
> There's been a lot of fuss made lately over memory inspection and profiling tools for Ruby implementations. And it's not without reason; inspecting a Ruby application's memory profile, much less diagnosing problems, has traditionally been very...

> **[Finding Leaks in Ruby Apps with Eclipse Memory Analyzer](http://blog.headius.com/2010/07/finding-leaks-in-ruby-apps-with-eclipse.html)**
>
> After my post on Browsing Memory the JRuby Way, one commenter and several other folks suggested I actually show using Eclipse MAT with JRuby. So without further ado...The Eclipse Memory Analyzer, like many Eclipse-based applications, starts up with a

- Charlie