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.1">
8
			<title>JMC 8.1 - New Release!</title>
9
			<description>
10
				This is a new minor release of Java Mission Control. The
11
				JMC application will now require JDK 11+ to run,
12
				but can still be
13
				used with OpenJDK 8u272+ and Oracle JDK 7u40+. It can
14
				also still open
15
				and visualize flight
16
				recordings from JDK 7 and 8.
17
			</description>
18
			<image>general/jmc.png</image>
19
		</note>
20
		<note version="8.1">
21
			<title>Eclipse 4.19 support</title>
22
			<description>
23
				The Mission Control client is now built to run optimally
24
				on Eclipse 2021-03 and later. To install Java Mission
25
				Control into
26
				Eclipse, go to the update site (Help | Install New Software...). The
27
				URL to the update site will be
28
				vendor specific, and some vendors will
29
				instead provide an archive with the update site.
30
			</description>
31
			<image>general/eclipse.png</image>
32
		</note>
33
		<note version="8.1">
34
			<title>Minor bugfixes and improvements</title>
35
			<description>
36
				There are more than 80 fixes and improvements in this release.
37
				Check out the JMC 8.1 Result Dashboard
38
				(https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=20404)
39
				for more information.
40
			</description>
41
			<image>general/issues.png</image>
42
		</note>
43
	</component>
44
	<component>
45
		<!-- ******************************* JMC Core ************************** -->
46
		<name>Core</name>
47
		<note version="8.1">
48
			<title>New Serializers Core Bundle</title>
49
			<description>
50
				There is now a new core bundle making it easy to
51
				serialize flight recording data to DOT (Graphviz) and JSon. This
52
				bundle will be expanded upon in future versions.
53
			</description>
54
			<image>core/serializers.png</image>
55
		</note>
56
		<note version="8.1">
57
			<title>Improved JFR parser performance</title>
58
			<description>
59
				The performance of the JFR parser has been improved.
60
				More improvements are coming in 8.2.
61
			</description>
62
			<image>core/parserperf.png</image>
63
		</note>
64
	</component>
65
	<component>
66
		<!-- ******************************* JFR ******************************* -->
67
		<name>Java Flight Recorder (JFR)</name>
68
		<note version="8.1">
69
			<title>Support for the new JDK 16 Allocation Events</title>
70
			<description>
71
				A new form of light weight allocation profiling was
72
				introduced with JDK 16 (see
73
				https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8257602).
74
				This version of JMC supports this new type of allocation profiling.
75
			</description>
76
			<image>jfr/allocationprof.png</image>
77
		</note>
78
		<note version="8.1">
79
			<title>New Page for Peeking into the Constant Pools</title>
80
			<description>
81
				There is a new page available for taking a look at what
82
				constants are available in the recording. This can, for example, be
83
				useful when creating custom events to see where all that storage and
84
				memory is being used.
85
			</description>
86
			<image>jfr/constantpool.png</image>
87
		</note>
88
		<note version="8.1">
89
			<title>Open Recordings with .lz4 extension</title>
90
			<description>
91
				For convenience, files with the .lz4 extension will now
92
				be attempted to be opened as flight recordings. This is since lz4 is
93
				a common compression to use with flight recordings.
94
			</description>
95
			<image>jfr/lz4.png</image>
96
		</note>
97
	</component>
98
	<!-- ******************************* Agent ******************************* -->
99
	<component>
100
		<name>JMC Agent Plug-in</name>
101
		<note version="8.1.0">
102
			<title>New JMC Agent Plug-in</title>
103
			<description>
104
				There is now a new agent plug-in available for JMC,
105
				which allows configuring where to emit flight recording
106
				events in an
107
				already running process.
108
			</description>
109
			<image>agent/agent.png</image>
110
		</note>
111
	</component>
112
	<!-- ******************************* Bugfixes ****************************************** -->
113
	<bugfixes>
114
		<bugfix>
115
			<area>JFR</area>
116
			<bugid>6939</bugid>
117
			<synopsis>Time range indicator update problem fixed</synopsis>
118
			<description>
119
				Sometimes the time range indicator wasn't updated when
120
				setting the time
121
				range. This is now fixed.
122
			</description>
123
		</bugfix>
124
		<bugfix>
125
			<area>JFR</area>
126
			<bugid>7007</bugid>
127
			<synopsis>
128
				Unable to edit run configurations for eclipse project after
129
				installing JMC
130
				plugin fixed
131
			</synopsis>
132
			<description>
133
				Previously it would not be possible to edit run
134
				configuration after installing
135
				the experimental JMC launcher plug-in.
136
				This has now been resolve.
137
			</description>
138
		</bugfix>
139
	</bugfixes>
140
	<!-- ******************************* Known issues ****************************************** -->
141
	<knownissues>
142
		<issue>
143
			<area>General</area>
144
			<bugid>4270</bugid>
145
			<synopsis>Hibernation and time</synopsis>
146
			<description>
147
				After the bugfix of
148
				https://bugs.openjdk.java.net/browse/JDK-6523160 in JDK 8, the
149
				RuntimeMXBean#getUptime() attribute was re-implemented to mean
150
				"Elapsed time of JVM process", whilst it previously was implemented
151
				as time since start of the JVM process. The uptime attribute is used
152
				by JMC, together with RuntimeMXBean#getStartTime(), to estimate the
153
				actual server time. This means that time stamps, as well as
154
				remaining time for a flight recording, can be wrong for processes on
155
				machines that have been hibernated.
156
			</description>
157
		</issue>
158
		<issue>
159
			<area>JFR</area>
160
			<bugid>7071</bugid>
161
			<synopsis>JMC can't attach to jlinked JVMs</synopsis>
162
			<description>
163
				This one is still under investigation, but it seems JMC
164
				can't attach to certain jlinked images.
165
			</description>
166
		</issue>
167
		<issue>
168
			<area>JFR</area>
169
			<bugid>7068</bugid>
170
			<synopsis>
171
				JfrRecordingTest (uitest) hangs on the automated analysis
172
				page
173
			</synopsis>
174
			<description>
175
				Trying to run uitests on Fedora hangs on
176
				JfrRecordingTest.
177
			</description>
178
		</issue>
179
		<issue>
180
			<area>JFR</area>
181
			<bugid>7003</bugid>
182
			<synopsis>The graph and flame graph view does not work on Windows
183
			</synopsis>
184
			<description>
185
				This is due to a bug with the Edge based browser
186
				component in SWT. We'll look into it for 8.2.0.
187
			</description>
188
		</issue>
189
		<issue>
190
			<area>JFR</area>
191
			<bugid>6265</bugid>
192
			<synopsis>JMC crashes with Webkit2+GTK 4</synopsis>
193
			<description>See the issue for more information.</description>
194
		</issue>
195
		<issue>
196
			<area>JFR</area>
197
			<bugid>5412</bugid>
198
			<synopsis>Dragging and dropping a JFR file into an open analysis page
199
				does not work
200
			</synopsis>
201
			<description>
202
				The expected behaviour would be to open the recording
203
				whenever a file is dropped in the editor area, but the behaviour
204
				will be defined by the embedded browser component, and not very
205
				useful.
206
			</description>
207
		</issue>
208
	</knownissues>
209
</notes>
210