Thanks for your reply! Well it looks like it only took one hour more to find out what was wrong. It wasn’t just the one reference to the jsweakrefdi factory that was wrong. I in fact had to replace the entire block of code that initialized that factory – it was also invoking a set method instead of a get method.

I look forward to trying out the program more and seeing more updates come out of the pipeline! Again, I appreciate your response – its great to know that when you put yourself out there someone actually is listening :)

Can’t wait to test future releases!

Kevin

We will have a new version of the app out hopefully this week that should be a lot easier for you…. sorry for the pain.

Cheers,

Dion

I understand the build is not in final, but I am having some significant issues trying to deploy this application.

Just to be clear – I downloaded and installed the Jetpack addon for FF 3.5 Windows, I navigated to the memory-profiler…html page and clicked the link – nothing happened. I navigated to c:/documents and settings/..memory-profiler-server.html and changed the reference from jsweakrefdi TO jetpackdi per your recommendation.

Restarted FF and still no initialization of Server. I’ve been working on this for about 12 hours now because my web app is leaking memory and I’d kill to just have a glimpse of the memory allocation.

If you could shed some light on anything I may have missed, could you let me know? I’ll throw some karma your way!

Kevin

Therefore, I decided to take a look and I have downloaded and installed this to see how this tool could help me. To start, I had to fix an issue in the profiler server, which was still pointing to the old ‘jsweakrefdi’ factory, which has been renamed to ‘jetpackdi’. After changing that I could start working..

For this to work you need to different browsers (every instance of Firefox will really freeze) but the tool had some issues with other browsers (IE was giving a script error on showing the heap dump, Chrome was not able to browse through the tree). But it’s a prototype, so I did not expect full functionality.

There are a couple of things I would like to see improve in next versions:
-1- Browsing through the object tree will cause a loss of context (how do I get back after clicking some object and where am I?). Probably better to build up a subtree while clicking on an object reference (solves both).
-2- It is not clear to me what I see in the quick look tab?
-3- The heap dump shows now objects and functions mixed. I think it would be nice to distinguish between those two (as VisualVM does with Heap and NonHeap)
-4- It is very handy when you are able to see the content of simple type fields in an object (like the content of a String, Number or Boolean field).
-5- Besides being able to see in the heap dump which instances of a specific type are available with there referrers, it would also be great to see that on the meta level (meaning that you see which types are referring to each other with the amount of instances as this gives a quick insight in the ‘hotspots’).

Besides that, what I currently saw in the ‘heap dump’ was nearly only a list of functions (including prototype methods), while I was expecting a list of object types? Also a lot of ‘internal’ firefox and jetpack functions where shown there (can those be filtered out?).

I hope to see this tool grow and provide valuable information like memory profilers as VisualVM and YourKit do. When do you expect this to be ready ;)? (I can’t wait..)

You mean, something like Opera’s Dragonfly? Ok, maybe the fact that Opera didn’t succeed doesn’t mean that if Firefox reinvents the wheel, it will do better (it does have a much larger developer codebase), but I don’t think you can expect that Opera is going to implement your API when they have their own (as far as I understood). And since neither you nor Webkit implemented Opera’s API, what’s the chance that Webkit is going to implement your api?

What will happen is that Webkit will have their own API, incompatible with everyone elses API.