Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315940

Summary: Remember custom JDK that is set for Acquire Heap Dump
Product: [Tools] MAT Reporter: Dominik Stadler <dominik.stadler>
Component: GUIAssignee: Project Inbox <mat.gui-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Dominik Stadler CLA 2010-06-07 04:50:44 EDT 
Build Identifier: Eclipse Memory Analyzer Version 1.0.0

Currently the jdkhome property is always reset, this means users that need to use a different JDK for heap dump retrieval need to always enter the different one, it would be more user friendly to have the last custom jdk remembered for this field as you typically do a number of memory dumps of the same application during memory analysis.

I typically have to set a different JDK when my "system under analysis" is running with 32-bit, whereas MAT is executed with 64-bit (necessary to have more memory available than 2G).

Reproducible: Always

Steps to Reproduce:
1. Acquire a heap dump where you set the jdkhome to a different value
2. Acquire another heap dump, the jdkhome property is reset to the default value instead of the value you just entered before
Comment 1 Krum Tsvetkov CLA 2010-06-24 06:16:35 EDT 
I checked in some changes which solve the problem.
Previously only the user setting for the JDK used to get the list of JVMs was saved and this was reused for calling jmap. It was possible to choose another VM for jmap but this specific setting wasn't saved. Now both of them are saved as separate properties.

The change will be included in the next bugfix release, which I (tentatively) see in about a month. Until then as a workaround for your problem you can use the "Configure" button on the first page and set there the jdkHome used to get the list of VMs to the x32 one. As I said this one is used then to call jmap.