Memory snapshot before / after GC?

[abcde]

Forgive me if I'm asking in the wrong place for this.

I'd like to take a snapshot of my application's memory usage BEFORE a GC is performed. I suspect there is a memory leak / unnecessary object creation going on somewhere in my app, and would like to see a diff of before/after the full GC. A the profiler forces a GC as soon as I hit 'take memory snapshot', I can't see this data.

Are you aware of how I could view this?

[jessica.ramos]

Thanks very much for your post!

Unfortunately though, there isn't a way you can take a snapshot without forcing a garbage collection. This is for good reason though--without taking a garbage collection, the snapshot would include objects that were still in memory but didn't have any references to them. This could be misleading and also interfere with snapshot comparisons.

I realize you're concerned about the objects created and cleaned up between garbage collections, however I don't think you need to worry about these. To quote one of our artcles:

[abcde]

I'm essentially trying to identify sources of memory churn - I think a before/after GC snapshot would help here, but understand why it's not supported.

Thanks