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.2">
8
			<title>JMC 8.2 - 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.
15
			</description>
16
			<image>general/jmc.png</image>
17
		</note>
18
		<note version="8.2">
19
			<title>Eclipse 4.22 support</title>
20
			<description>
21
				The Mission Control client is now built to run optimally
22
				on Eclipse 2021-06 and later. To install JDK Mission Control into
23
				Eclipse, go to the update site (Help | Install New Software...). The
24
				URL to the update site will be vendor specific, and some vendors
25
				will instead provide an archive with the update site.
26
			</description>
27
			<image>general/eclipse.png</image>
28
		</note>
29
		<note version="8.2">
30
			<title>Minor bugfixes and improvements</title>
31
			<description>
32
				There are 83 fixes and improvements in this release.
33
				Check out the JMC 8.2 Result Dashboard
34
				(https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=20804)
35
				for more information.
36
			</description>
37
			<image>general/issues.png</image>
38
		</note>
39
		<note version="8.2">
40
			<title>Binary build for Apple ARM</title>
41
			<description>
42
				JDK Mission Control is now built for Apple ARM, allowing
43
				JMC to be run natively (without Rosetta x86 emulation) on Apple M1.
44
			</description>
45
			<image>general/apple.png</image>
46
		</note>
47
	</component>
48
	<component>
49
		<!-- ******************************* JMC Core ************************** -->
50
		<name>Core</name>
51
		<note version="8.2">
52
			<title>Parser support for async profiler</title>
53
			<description>
54
				Parser support has been added for frame types generated
55
				by async profiler, such as Native, C++ and Kernel.
56
			</description>
57
			<image>special/noimage.png</image>
58
		</note>
59
		<note version="8.2">
60
			<title>System.gc() rule</title>
61
			<description>
62
				There is now a new rule for explicit invocations of
63
				System.gc().
64
			</description>
65
			<image>core/dukegc.png</image>
66
		</note>
67
	</component>
68
	<component>
69
		<!-- ******************************* JFR ******************************* -->
70
		<name>Java Flight Recorder (JFR)</name>
71
		<note version="8.2">
72
			<title>Heat map view</title>
73
			<description>
74
				A new heat map view has been added, which is handy for
75
				seeing when events are taking place. Use Window | Show View | Other...,
76
				and select the Heatmap View under Mission Control and click Open to
77
				open the view.
78
			</description>
79
			<image>jfr/heatmap.png</image>
80
		</note>
81
		<note version="8.2">
82
			<title>Websocket for selections</title>
83
			<description>
84
				There is a new websocket API available that pushes stack
85
				trace data from selections in the JFR UI as JSON on a user defined
86
				port. This allows for programmatic control of the visualization
87
				directly in the browser. Tools like observablehq.com can be used to
88
				invent new visualizations, or to alter the visualization. To get
89
				started, simply go to the Flight Recorder preferences in JMC, and
90
				select the Websocket port to use (0 to disable). A set of example
91
				visualizations are available here:
92
				https://observablehq.com/collection/@cimi/java-mission-control.
93
			</description>
94
			<image>jfr/websocket.png</image>
95
		</note>
96
	</component>
97
	<!-- ******************************* Agent ******************************* -->
98
	<!-- <component> <name>JMC Agent Plug-in</name> <note version="8.1.0"> <title>New 
99
		JMC Agent Plug-in</title> <description> There is now a new agent plug-in 
100
		available for JMC, which allows configuring where to emit flight recording 
101
		events in an already running process. </description> <image>agent/agent.png</image> 
102
		</note> </component> -->
103
	<!-- ******************************* Bugfixes ****************************************** -->
104
	<bugfixes>
105
		<bugfix>
106
			<area>JFR</area>
107
			<bugid>7403</bugid>
108
			<synopsis>JFR parser struct types hashcode problem</synopsis>
109
			<description>
110
				Some JFR parser struct types were using lazily
111
				initialized attributes which happen to be a part of hashCode/equals
112
				computations.
113
			</description>
114
		</bugfix>
115
		<bugfix>
116
			<area>JFR</area>
117
			<bugid>7532</bugid>
118
			<synopsis>
119
				Delays in rendering of JMX console graphs
120
			</synopsis>
121
			<description>
122
				Sometimes the updates of the JMX console graphs would be
123
				severely delayed on MacOS. This is now fixed.
124
			</description>
125
		</bugfix>
126
		<bugfix>
127
			<area>JFR</area>
128
			<bugid>7068</bugid>
129
			<synopsis>
130
				JfrRecordingTest (uitest) hangs on the automated analysis
131
				page
132
			</synopsis>
133
			<description>
134
				Trying to run uitests on Fedora hangs on JfrRecordingTest. 
135
				This was fixed after the Eclipse platform update.
136
			</description>
137
		</bugfix>
138
	</bugfixes>
139
	<!-- ******************************* Known issues ****************************************** -->
140
	<knownissues>
141
		<issue>
142
			<area>General</area>
143
			<bugid>4270</bugid>
144
			<synopsis>Hibernation and time</synopsis>
145
			<description>
146
				After the bugfix of
147
				https://bugs.openjdk.java.net/browse/JDK-6523160 in JDK 8, the
148
				RuntimeMXBean#getUptime() attribute was re-implemented to mean
149
				"Elapsed time of JVM process", whilst it previously was implemented
150
				as time since start of the JVM process. The uptime attribute is used
151
				by JMC, together with RuntimeMXBean#getStartTime(), to estimate the
152
				actual server time. This means that time stamps, as well as
153
				remaining time for a flight recording, can be wrong for processes on
154
				machines that have been hibernated.
155
			</description>
156
		</issue>
157
		<issue>
158
			<area>JFR</area>
159
			<bugid>7071</bugid>
160
			<synopsis>JMC can't attach to jlinked JVMs</synopsis>
161
			<description>
162
				This one is still under investigation, but it seems JMC
163
				can't attach to certain jlinked images.
164
			</description>
165
		</issue>
166
		<issue>
167
			<area>JFR</area>
168
			<bugid>7003</bugid>
169
			<synopsis>The graph and flame graph view does not work on Windows
170
			</synopsis>
171
			<description>
172
				This is due to a problem with the Windows based browser
173
				component in SWT. We're hoping for a fix in the component for a
174
				future version of the Eclipse platform.
175
			</description>
176
		</issue>
177
	</knownissues>
178
</notes>
179