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.3">
8
			<title>JMC 8.3 - New Release!</title>
9
			<description>
10
				This is a new minor release of JDK Mission Control. The
11
				JMC application requires JDK 11+ to run, but can still be used to
12
				connect to, and parse JFR recordings from, OpenJDK 8u272+ and Oracle
13
				JDK 7u40+. It can also still open and visualize flight recordings
14
				from JDK 7 and 8. JDK Mission Control is built for Windows (x86_64), 
15
				Mac OS X (ARM and x86_64), as well as Linux (x86_64).
16
			</description>
17
			<image>general/jmc.png</image>
18
		</note>
19
		<note version="8.3">
20
			<title>Eclipse 4.24 support</title>
21
			<description>
22
				The Mission Control client is now built to run optimally
23
				on Eclipse 2022-06 and later. To install JDK Mission Control into
24
				Eclipse, go to the update site (Help | Install New Software...). The
25
				URL to the update site will be vendor specific, and some vendors
26
				will instead provide an archive with the update site.
27
			</description>
28
			<image>general/eclipse.png</image>
29
		</note>
30
		<note version="8.3">
31
			<title>Minor bugfixes and improvements</title>
32
			<description>
33
				There are 51 fixes and improvements in this release.
34
				Check out the JMC 8.3 Result Dashboard
35
				(https://bugs.openjdk.org/secure/Dashboard.jspa?selectPageId=21205)
36
				for more information.
37
			</description>
38
			<image>general/issues.png</image>
39
		</note>
40
	</component>
41
	<component>
42
		<!-- ******************************* JMC Core ************************** -->
43
		<name>Core</name>
44
		<note version="8.3">
45
			<title>Parser improvements</title>
46
			<description>
47
				The performance of the FastAccessNumberMap has been improved
48
				for sparse values.
49
			</description>
50
			<image>special/noimage.png</image>
51
		</note>
52
	</component>
53
	<component>
54
		<!-- ******************************* JFR ******************************* -->
55
		<name>Java Flight Recorder (JFR)</name>
56
		<note version="8.3">
57
			<title>Dependency View</title>
58
			<description>
59
				There is a new view for visualizing call dependencies. There are 
60
				two modes of operation in the view, chord diagram and edge bundling.
61
				In the edge bundling visualization, hover over packages to see
62
				dependencies highlighted in colors: green means that methods in the 
63
				linked package is called by methods in the package being hovered over, 
64
				yellow means that methods in the linked package are calling mathods in
65
				the package being hovered over. Red means that methods in the packages
66
				are calling each other. To show the Dependency View, go to Window | Show View | 
67
				Other... and select the Dependency View under the Mission Control folder. 
68
			</description>
69
			<image>jfr/dependency.png</image>
70
		</note>
71
		<note version="8.3">
72
			<title>Graph Pruning</title>
73
			<description>
74
				The graph view in JMC can now be pruned to focus on the most impactful 
75
				nodes. Select the target number of nodes, and the visualization will 
76
				show at most that many number of nodes.
77
			</description>
78
			<image>jfr/graphpruning.png</image>
79
		</note>
80
		<note version="8.3">
81
			<title>Selectable Attribute</title>
82
			<description>
83
				It is now possible to select which attribute to use for the weights
84
				in the trace view and the flame graph view.
85
			</description>
86
			<image>jfr/attribute.png</image>
87
		</note>
88
		<note version="8.3">
89
			<title>Parser improvement</title>
90
			<description>
91
				The parser now supports parsing events with char fields.
92
			</description>
93
			<image>special/noimage.png</image>
94
		</note>
95
	</component>
96
	<!-- ******************************* Agent ******************************* -->
97
	<!-- <component> <name>JMC Agent Plug-in</name> <note version="8.1.0"> <title>New 
98
		JMC Agent Plug-in</title> <description> There is now a new agent plug-in 
99
		available for JMC, which allows configuring where to emit flight recording 
100
		events in an already running process. </description> <image>agent/agent.png</image> 
101
		</note> </component> -->
102
	<!-- ******************************* Bugfixes ****************************************** -->
103
	<bugfixes>
104
		<bugfix>
105
			<area>General</area>
106
			<bugid>7813</bugid>
107
			<synopsis>
108
				Unable to open Help page in macOS M1 when JMC started with JDK11
109
			</synopsis>
110
			<description>
111
				The help page was inaccessible, throwing an error on macOS M1 
112
				when JMC is run on JDK 11.0.16. This is now fixed.
113
			</description>
114
		</bugfix>
115
		<bugfix>
116
			<area>General</area>
117
			<bugid>7321</bugid>
118
			<synopsis>
119
				Unable to view JMC Help Contents (HTTP ERROR 500 ) when booted with JDK 17 or higher
120
			</synopsis>
121
			<description>
122
				The help page was inaccessible, throwing an error, when running on JDK 17+.
123
				This is now fixed.
124
			</description>
125
		</bugfix>
126
		<bugfix>
127
			<area>JFR</area>
128
			<bugid>7812</bugid>
129
			<synopsis>Unable to open links from Automated Result analysis page</synopsis>
130
			<description>
131
				Links in the results of the automated analysis results would not
132
				open properly on Linux and Mac OS X. Now they do open in situ.
133
			</description>
134
		</bugfix>
135
	</bugfixes>
136
	<!-- ******************************* Known issues ****************************************** -->
137
	<knownissues>
138
		<issue>
139
			<area>General</area>
140
			<bugid>4270</bugid>
141
			<synopsis>Hibernation and time</synopsis>
142
			<description>
143
				After the bugfix of
144
				https://bugs.openjdk.java.net/browse/JDK-6523160 in JDK 8, the
145
				RuntimeMXBean#getUptime() attribute was re-implemented to mean
146
				"Elapsed time of JVM process", whilst it previously was implemented
147
				as time since start of the JVM process. The uptime attribute is used
148
				by JMC, together with RuntimeMXBean#getStartTime(), to estimate the
149
				actual server time. This means that time stamps, as well as
150
				remaining time for a flight recording, can be wrong for processes on
151
				machines that have been hibernated.
152
			</description>
153
		</issue>
154
		<issue>
155
			<area>JFR</area>
156
			<bugid>7071</bugid>
157
			<synopsis>JMC can't attach to jlinked JVMs</synopsis>
158
			<description>
159
				This one is still under investigation, but it seems JMC
160
				can't attach to certain jlinked images.
161
			</description>
162
		</issue>
163
		<issue>
164
			<area>JFR</area>
165
			<bugid>7003</bugid>
166
			<synopsis>The graph, flame graph view, heatmap view and dependency view does not work on 
167
Windows
168
			</synopsis>
169
			<description>
170
				This is due to a problem with the Windows based browser
171
				component in SWT. We're hoping for a fix in the component for a
172
				future version of the Eclipse platform.
173
			</description>
174
		</issue>
175
	</knownissues>
176
</notes>
177