jmc

1
<?xml version="1.0" encoding="ISO-8859-1"?>
2
<?xml-stylesheet type="text/xsl" href="stylesheet.xsl"?>
3
<notes>
4
	<component>
5
		<!--  ******************************* GENERAL ****************************************** -->
6
		<name>General</name>
7
		<note version="8.0">
8
			<title>JMC 8.0 - Major New Release!</title>
9
			<description>
10
				This is a major new release of Java Mission Control. All binary build of the JMC application using the
11
				Eclipse 2020-09 platform will now require JDK 11+ to run, but can be used with OpenJDK 8u272+ and Oracle JDK 7u40+.
12
				It can also open and visualize flight recordings from JDK 7 and 8.
13
			</description>
14
			<image>general/jmc.png</image>
15
		</note>
16
		<note version="8.0">
17
			<title>Eclipse 4.16 support</title>
18
			<description>
19
				The Mission Control client is now built to run optimally on Eclipse 2020-06 and later. To install Java Mission
20
				Control into Eclipse, go to the update site (Help | Install New Software...). The URL to the update site will be
21
				vendor specific, and some vendors will instead provide an archive with the update site.
22
			</description>
23
			<image>general/eclipse.png</image>
24
		</note>
25
		<note version="8.0">
26
			<title>JOverflow in the Base Distribution</title>
27
			<description>
28
				JOverflow is now part of the base distribution of Mission Control, and has been converted to SWT. It also has a brand  
29
				new TreeMap visualization of the heap occupied by type. To open the new view, go to Window | Show view |
30
				Other... and start typing JOverflow, and select JOverflow TreeMap.
31
			</description>
32
			<image>general/joverflow.png</image>
33
		</note>
34
		<note version="8.0">
35
			<title>Minor bugfixes and improvements</title>
36
			<description>
37
				There are over two hundred fixes and improvements in this release. Check out the JMC 8 Result Dashboard 
38
				(https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=19536") for more information.
39
			</description>
40
			<image>general/issues.png</image>
41
		</note>
42
	</component>
43
	
44
	<!--  ******************************* JFR ******************************* -->
45
	<component>
46
		<name>Java Flight Recorder (JFR)</name>
47
		<note version="8.0">
48
			<title>Flame Graph View Improvements</title>
49
			<description>
50
				The Flame Graph View is now available in the standard perspective. It can now be configured to be
51
				rendered either as an icicle graph or a flame graph, and the tool tips have been improved. Click on anything
52
				representing a selection of events to get the aggregate of stack traces represented by that selection rendered in
53
				the Flame Graph View.
54
			</description>
55
			<image>jfr/flameview.gif</image>
56
		</note>
57
		<note version="8.0">
58
			<title>New Graph View</title>
59
			<description>
60
				An early access version of a Graph View is now available. The Graph View will show a directed graph
61
				where the individual methods are nodes in the graphs, and the edges will represent calls from one method to another.
62
				The size of the node will represent the "self" contribution, and the thickness of an edge will correlate with the
63
				number of calls from one method to another in the events. To open up the graph view, go to Window | Show view |
64
				Other..., then select Mission Control / Graph View. Once the Graph View has opened, it can be docked where you want
65
				it to be, or dragged out into a new top level window which can be handled by your window manager. Currently there is
66
				no graph pruning, and large graph will take a very long time to layout and render, during which the UI will freeze.
67
				Therefore we've imposed a user configurable limit on the number of nodes a graph can have for now.
68
			</description>
69
			<image>jfr/graphview.gif</image>
70
		</note>
71
		<note version="8.0">
72
			<title>Predecessors and Successors</title>
73
			<description>
74
				The predecessors and successors tabs have been brought back to the Method Profiling page. This means
75
				that it is now easy to select a method and easily see wherever that method was called from, and to see what was then
76
				called from that method. This is a temporary solution until we have a separate Butterfly/Sandwich view where any
77
				selection of a method in a set of events can be rendered in a separately configured view.
78
			</description>
79
			<image>jfr/predsuc.png</image>
80
		</note>
81
	</component>
82
	<component>
83
		<!--  ******************************* Agent ******************************* -->
84
		<name>JMC Agent</name>
85
		<note version="1.0.0">
86
			<title>Agent 1.0.0</title>
87
			<description>
88
				This is the first version where we build and release the JMC agent. The JMC agent is a byte code
89
				instrumentation agent, providing an easy way to declaratively generate JFR events from most methods, even methods 
90
				for which the source code is not available. Either configure the agent with an XML configuration file, or use the
91
				MBean to dynamically change the instrumentation whilst the application is running.
92
			</description>
93
			<image>agent/agent.png</image>
94
		</note>
95
		<note version="1.0.0">
96
			<title>Converter Functions</title>
97
			<description>
98
				Now any public static method can be used to convert objects of a specific type to one of the types
99
				supported by flight recorder. The converter to use must be explicitly declared per recorded data.
100
			</description>
101
			<image>agent/converter.png</image>
102
		</note>
103
	</component>
104
	<!--  ******************************* Bugfixes ****************************************** -->
105
	<bugfixes>
106
		<bugfix>
107
			<area>JFR</area>
108
			<bugid>5734</bugid>
109
			<synopsis>Overflow in stacktrace tooltips fixed</synopsis>
110
			<description>On Mac, the tooltips shown for the stacktraces could overflow. This is now fixed.</description>
111
		</bugfix>
112
	</bugfixes>
113
	<!--  ******************************* Known issues ****************************************** -->
114
	<knownissues>
115
		<issue>
116
			<area>General</area>
117
			<bugid>4270</bugid>
118
			<synopsis>Hibernation and time</synopsis>
119
			<description>
120
				After the bugfix of https://bugs.openjdk.java.net/browse/JDK-6523160 in JDK 8, the
121
				RuntimeMXBean#getUptime() attribute was re-implemented to mean "Elapsed time of JVM process", whilst it previously
122
				was implemented as time since start of the JVM process. The uptime attribute is used by JMC, together with
123
				RuntimeMXBean#getStartTime(), to estimate the actual server time. This means that time stamps, as well as remaining
124
				time for a flight recording, can be wrong for processes on machines that have been hibernated.
125
			</description>
126
		</issue>
127
		<issue>
128
			<area>General</area>
129
			<bugid>4270</bugid>
130
			<synopsis>Hibernation and time</synopsis>
131
			<description>
132
				After the bugfix of https://bugs.openjdk.java.net/browse/JDK-6523160 in JDK 8, the
133
				RuntimeMXBean#getUptime() attribute was re-implemented to mean "Elapsed time of JVM process", whilst it previously
134
				was implemented as time since start of the JVM process. The uptime attribute is used by JMC, together with
135
				RuntimeMXBean#getStartTime(), to estimate the actual server time. This means that time stamps, as well as remaining
136
				time for a flight recording, can be wrong for processes on machines that have been hibernated.
137
			</description>
138
		</issue>
139
		<issue>
140
			<area>JFR</area>
141
			<bugid>7122</bugid>
142
			<synopsis>Rules evaluation never complete</synopsis>
143
			<description>Sometimes the rules evaluation may never complete for the GC rules.</description>
144
		</issue>
145
		<issue>
146
			<area>JFR</area>
147
			<bugid>7071</bugid>
148
			<synopsis>JMC can't attach to jlinked JVMs</synopsis>
149
			<description>This one is still under investigation, but it seems JMC can't attach to certain jlinked images.
150
			</description>
151
		</issue>
152
		<issue>
153
			<area>JFR</area>
154
			<bugid>7068</bugid>
155
			<synopsis>JfrRecordingTest (uitest) hangs on the automated analysis page</synopsis>
156
			<description>Trying to run uitests on Fedora hangs on JfrRecordingTest.</description>
157
		</issue>
158
		<issue>
159
			<area>JFR</area>
160
			<bugid>7007</bugid>
161
			<synopsis>Unable to edit run configurations for eclipse project after installing JMC plugin</synopsis>
162
			<description>Avoid installing the experimental JMC launcher plug-in into Eclipse until this problem has been
163
				resolved.
164
			</description>
165
		</issue>
166
		<issue>
167
			<area>JFR</area>
168
			<bugid>7003</bugid>
169
			<synopsis>The graph view does not work on Windows</synopsis>
170
			<description>This is due to a bug in the chromium browser plug-in used by JMC on Windows. See the issue for more
171
				information.
172
			</description>
173
		</issue>
174
		<issue>
175
			<area>JFR</area>
176
			<bugid>6265</bugid>
177
			<synopsis>JMC crashes with Webkit2+GTK 4</synopsis>
178
			<description>See the issue for more information.</description>
179
		</issue>
180
		<issue>
181
			<area>JFR</area>
182
			<bugid>6265</bugid>
183
			<synopsis>JMC crashes with Webkit2+GTK 4</synopsis>
184
			<description>See the issue for more information.</description>
185
		</issue>
186
		<issue>
187
			<area>JFR</area>
188
			<bugid>5412</bugid>
189
			<synopsis>Dragging and dropping a JFR file into an open analysis page does not work</synopsis>
190
			<description>The expected behaviour would be to open the recording whenever a file is dropped in the editor area, but
191
				the behaviour will be defined by the embedded browser component, and not very useful.
192
			</description>
193
		</issue>
194
	</knownissues>
195
</notes>