-
Notifications
You must be signed in to change notification settings - Fork 3
/
configure_mat.html
572 lines (394 loc) · 25.5 KB
/
configure_mat.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="generator" content="DITA-OT" /><meta name="DC.type" content="task" />
<meta name="DC.title" content="Memory Analyzer Configuration" />
<meta name="copyright" content="Copyright (c) 2008, 2023 SAP AG and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0 which accompanies this distribution, and is available at https://www.eclipse.org/legal/epl-2.0/ " type="primary" />
<meta name="DC.rights.owner" content="Copyright (c) 2008, 2023 SAP AG and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0 which accompanies this distribution, and is available at https://www.eclipse.org/legal/epl-2.0/ " type="primary" />
<meta name="DC.format" content="XHTML" />
<meta name="DC.identifier" content="task_configure_mat" />
<meta name="DC.language" content="en-us" />
<link rel="stylesheet" type="text/css" href="../styles/commonltr.css" />
<title>Memory Analyzer Configuration</title>
</head>
<body id="task_configure_mat">
<h1 class="title topictitle1" id="ariaid-title1">Memory Analyzer Configuration</h1>
<div class="body taskbody">
<div class="section context">
<p class="p">
Well, analyzing big heap dumps can also require more heap space.
Give it
some more memory (possible by running on a 64-bit machine):
</p>
<code class="ph codeph">MemoryAnalyzer.exe -vmargs -Xmx4g</code>
<p class="p">Alternatively, edit the MemoryAnalyzer.ini to
contain:</p>
<div class="p">
<pre class="pre codeblock"><code>-vmargs
-Xmx4g</code></pre>
</div>
<p class="p">
For more details, check out the section
<a class="xref" href="http://help.eclipse.org/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm">Running Eclipse</a>
in the Help Center. It also contains more details if you are running
on Mac OS X.
</p>
<p class="p">If you are running the Memory Analyzer inside your Eclipse SDK,
you need to edit the eclipse.ini file.</p>
<p class="p">The memory intensive parts are the parsing of the dump and building
of the dominator tree. Try parsing the heap
dump from the command line, perhaps on a bigger machine. The dumps
and index files can then be copied to a more convenient machine.
Once the dump has been parsed, it usually can
be opened with less memory in the GUI.
As a rough estimate if the number of objects is N and the number of
classes C, it might take at least T bytes to parse and build the dominator tree
where:
<code class="ph codeph">T ≈ N * 28.25 + C * 1000 + P</code>
P is the space used by the DTFJ or HPROF parsers. For a PHD file, the space could be:
<code class="ph codeph">P ≈ C * 1000</code>
Memory Analyzer uses additional memory for caching index files, so
performance will be better if there is more memory available than the minimum
required to parse a dump.
</p>
<p class="p">Memory Analyzer has an architectural limit of 2<sup class="ph sup">31</sup> - 3 objects,
a current limit of 2<sup class="ph sup">31</sup> - 9 = 2,147,483,639 objects, but has not been
tested with that many objects. The current record is a heap dump file of 159Gbytes
containing 2,041,300,061 objects, which was opened with Memory Analyzer running
with a 172Gbyte heap.
Exceeding the limit can result in an exception such as
<samp class="ph systemoutput">java.lang.OutOfMemoryError: Requested length of new long[2,147,483,640] exceeds limit of 2,147,483,639</samp>.
See <a class="xref" href="#task_configure_mat__discard">enable discard</a>
for options to work around this limit.</p>
<p class="p">The preference page is opened via a menu option.
<span class="ph menucascade"><span class="ph uicontrol">Window</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Preferences</span></span>
</p>
<div class="p" id="task_configure_mat__preferences">The preferences page allows various aspects of Memory Analyzer to be controlled.
Use the <a class="xref" href="javascript:executeCommand(%22org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.mat.ui.Preferences)%22)">
<strong class="ph b">Preferences</strong></a> dialog pages to set how you want Eclipse Memory Analyzer to operate. The menu path is
<span class="ph menucascade"><span class="ph uicontrol">Window</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Preferences</span></span>
on Windows and Linux -
on macOS the Preferences can be found in the "App" menu.
Some of the preferences can also be controlled from the command line in
<a class="xref" href="batch.html">batch mode</a>.
<img class="image" src="../mimes/preferences.png" alt="preferences page showing general options with DTFJ subpage" />
<dl class="dl">
<dt class="dt dlterm">Keep unreachable objects</dt>
<dd class="dd">Objects that appear unreachable from GC roots are not discarded in an early stage of
Memory Analyzer processing, but are retained for further analysis.</dd>
<dt class="dt dlterm">Hide the getting started wizard</dt>
<dd class="dd">Controls whether to display a wizard for leak suspects, top components after opening
a snapshot.</dd>
<dt class="dt dlterm">Hide popup query help</dt>
<dd class="dd">Do not display the help panel underneath the query wizard, unless F1 or the help button
is pressed.</dd>
<dt class="dt dlterm">Hide the Welcome screen on launch</dt>
<dd class="dd">The welcome page has the 'Overview' and 'Tutorials' tabs and the 'Workbench' button.
The welcome page is closed by going to the workbench.
Selecting this option means that when Memory Analyzer is started the workbench is displayed
first.
The welcome page can be reopened from the workbench by:
<span class="ph menucascade"><span class="ph uicontrol">Help</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Welcome</span></span>
</dd>
<dt class="dt dlterm">Bytes Display</dt>
<dd class="dd">
<p class="p">
There is a option (from MAT 1.5 onwards) to display bytes in B, KB, MB, GB, or Smart formats.
The default is to always display in Bytes format to match the previous MAT behavior and not cause any confusion.
The option can be changed in the Eclipse preference dialog or using <span class="keyword option">-Dbytes_display=(bytes|kilobytes|megabytes|gigabytes|smart)</span>.
</p>
<img class="image" src="../mimes/size_units_cfg.png" alt="Preferences dialog to configure size units" />
<dl class="dl">
<dt class="dt dlterm">Bytes (B)</dt>
<dd class="dd">Memory counted in single bytes</dd>
<dt class="dt dlterm">Kilobytes (KB)</dt>
<dd class="dd">Memory counted in units of 1,024 bytes</dd>
<dt class="dt dlterm">Megabytes (MB)</dt>
<dd class="dd">Memory counted in units of 1,048,576 bytes</dd>
<dt class="dt dlterm">Gigabytes (GB)</dt>
<dd class="dd">Memory counted in units of 1,073,741,824 bytes</dd>
<dt class="dt dlterm">Smart</dt>
<dd class="dd">In Smart mode, if the value is a gigabyte or more, display in gigabytes; similarly for megabytes and kilobytes; otherwise, display in bytes.
<img class="image" src="../mimes/size_units_sample.png" alt="A histogram showing entries with different size units" />
</dd>
</dl>
</dd>
<dt class="dt dlterm" id="task_configure_mat__expand">Expanded entries in tables and trees</dt>
<dd class="dd">There can be many rows in the tables and trees produced by queries.
This controls the number of new entries displayed after a double click
on the totals row, or for the <span class="ph menucascade"><span class="ph uicontrol">Next <span class="keyword option">N</span>n</span></span> menu item
or for expanding a tree entry
or for the number of rows for a table or tree in a report,
if not set by the <a class="xref" href="../doc/org/eclipse/mat/report/Params.Rendering.html#LIMIT"><span class="keyword parmname">limit</span></a>.
</dd>
<dt class="dt dlterm" id="task_configure_mat__discard">Enable discard (experimental)</dt>
<dd class="dd">
<p class="p">
Sometimes a heap dump is generated with more objects than Memory Analyzer
can handle, either from lack of heap to run Memory Analyzer itself, or because the number
exceeds the Memory Analyzer limit of 2,147,483,639 objects.
This option controls some experimental settings to help analyze
such huge dumps, by purposely discarding objects in the original
heap dump.
</p>
<p class="p">The discarded objects are counted in the
<a class="xref" href="../reference/inspections/unreachable_objects.html" title="Find out more about objects that could or should be garbage collected.">
unreachable objects histogram</a> together with any unreachable objects
discarded by Memory Analyzer after parsing but before building the dominator tree.
</p>
<p class="p">The discarded objects are not indexed, so are not part of the dominator tree
nor are they counted as part of the retained size. As they are not indexed they
will not appear in the <a class="xref" href="../reference/querymatrix.html#ref_querymatrix__list_objects">list objects</a>
query.
Most other queries will not operate on unindexed (discarded) objects.
Sometimes it is possible to view them. The inspector view can display
unindexed objects in the attributes and statics tabs.
It is possible to 'Go Into' an unindexed object from the inspector view, and
'Go Back' to the previous object.
Unindexed objects do not have GC root information, so in that
position in the inspector view is displayed a
<img class="image" src="../mimes/message_warning.png" alt="yellow warning triangle icon" />
warning triangle
and the message <samp class="ph msgph">Unindexed</samp>.
Names resolvers can use the values of unindexed objects to find a displayable
name for an object. This will be displayed after the object address
in the inspector view and in the
<a class="xref" href="../reference/tipsandtricks.html#ref_tips__value_tab">Inspector View value tab</a>.
</p>
<div class="p">Some trial and error may be required to find suitable values of the options.
<ol class="ol">
<li class="li">If an OutOfMemoryError still occurs on a parse then more objects need to be
discarded, either by increasing the discard percentage or by increasing the
number of types of discarded objects by changing the pattern.</li>
<li class="li">If the leak is
not apparent from the snapshot with many discarded objects then examine
the unreachable objects histogram to see if any key objects have been discarded
and modify the discard pattern. Ideally only primitive arrays or objects which
just have primitive fields or refer to primitive arrays should be discarded.
This avoids disrupting the object graph too much.</li>
<li class="li">If the types of the discarded objects look reasonable then try changing
which objects have been discarded, either by varying the offset (if the
discard percentage is not <kbd class="ph userinput">100</kbd>) or the discard seed.</li>
<li class="li">If the available heap to run Memory Analyzer is very small then try
discarding all of the ordinary objects by choosing <kbd class="ph userinput">100</kbd>
for the discard percentage and <kbd class="ph userinput">.*</kbd> to match all
object types. The resulting snapshot will not be useful for finding leaks,
but the unreachable object histogram will show the types of the objects
taking most of the heap space, and might give a hint as to the problem.</li>
</ol>
See <a class="xref" href="batch.html#task_batch__discard">
batch mode discard options</a> for controlling discard in batch
mode.
See <a class="xref" href="../reference/oqlsyntaxfrom.html#ref_oqlsyntaxfrom__unindexed">
OQL FROM clauses</a> for how to use OQL with unindexed objects.
</div>
<div class="note"><span class="notetitle">Note:</span> This feature is experimental and is subject to change
or removal. Please respond on the
<a class="xref" href="https://www.eclipse.org/forums/index.php/f/186/">
Memory Analyzer forum</a> if you try it and
find it useful or have suggestions.</div>
<dl class="dl">
<dt class="dt dlterm">Discard percentage</dt>
<dd class="dd">
A number between <kbd class="ph userinput">0</kbd> and <kbd class="ph userinput">100</kbd>, treated as a percentage.
Approximately this percentage of ordinary objects
matching the discard pattern will be
discarded by the HPROF or DTFJ parsers.
</dd>
<dt class="dt dlterm">Discard pattern</dt>
<dd class="dd">
Only objects with a class name matching this regular expression
will be discarded. It is best to chose objects of a type which
does not link to other objects, such as primitive arrays, or
objects which just link to other such objects. This avoids breaking
the object graph too much, and gives a hope that the leak
analysis will find the problem.
The default pattern of
<kbd class="ph userinput">char\[\]|java\.lang\.String</kbd> discards
character arrays and Strings. For Java 9 heap dumps with
compact strings based on byte arrays then
<kbd class="ph userinput">byte\[\]|java\.lang\.String</kbd> may be
more appropriate.
</dd>
<dt class="dt dlterm">Discard offset</dt>
<dd class="dd">
A number between <kbd class="ph userinput">0</kbd> and <kbd class="ph userinput">99</kbd>.
This allows different objects to be discarded from two different
parses of the same heap dump. This might be useful to allow objects
which have been discarded from one snapshot to be found in the
others. For example with a discard percentage of <kbd class="ph userinput">25</kbd>, then offsets
chosen from <kbd class="ph userinput">0</kbd>,<kbd class="ph userinput">25</kbd>,<kbd class="ph userinput">50</kbd>,<kbd class="ph userinput">75</kbd> in successive parses will discard
4 distinct sets of objects.
With a discard percentage of <kbd class="ph userinput">80</kbd>, and offsets of
<kbd class="ph userinput">0</kbd>,
<kbd class="ph userinput">20</kbd>,
<kbd class="ph userinput">40</kbd>,
<kbd class="ph userinput">60</kbd>,
<kbd class="ph userinput">80</kbd>
in successive parses, will have each object present in one of
those five snapshots.
</dd>
<dt class="dt dlterm">Discard seed</dt>
<dd class="dd">
This controls the starting point of the random number generator
used to decide whether to discard particular objects. If after
discarding objects the leak cannot be found then rerunning the
parse with a different seed would discard some different objects
and might show the leak better.
</dd>
</dl>
</dd>
<dt class="dt dlterm" id="task_configure_mat__dtfj_preferences">
<span class="ph menucascade"><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">DTFJ Parser</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Stack frames</span></span>
</dt>
<dd class="dd">
Normally stack frames are just shown in the Thread overview and stacks query.
This option allows stack frames to be treated as objects which are then visible like any other Java object in a Memory Analyzer view.
<dl class="dl">
<dt class="dt dlterm">Normal
</dt>
<dd class="dd">Stack frames are just shown in the Thread overview and stacks query.
</dd>
<dt class="dt dlterm">Only stack frames as pseudo-objects
</dt>
<dd class="dd">
Stack frames are of type <code class="ph codeph"><stack frame></code>, size 0, with method names and source file
and line numbers via fields and a name resolver.
<p class="p">This is useful when looking at paths to and from objects via local variables as the stack frames are visible in
the paths to GC roots queries.</p>
</dd>
<dt class="dt dlterm">Stack frames as pseudo-objects and running methods as pseudo-classes
</dt>
<dd class="dd">Stack frames of are of type <code class="ph codeph">packageName.className.methodName(Signature)ReturnType</code> extending <code class="ph codeph"><method></code> representing the method being executed,
of size the stack frame size, with source file and line number via fields and a name resolver,
and those methods are pseudo-classes of type <code class="ph codeph"><method type></code> of size 0.
<p class="p">This can be useful to find out which methods are currently running and how much stack space they take up.
To examine running methods then take the histogram view, filter by '\(', then sort by instances or instance size.
</p>
</dd>
<dt class="dt dlterm">Stack frames as pseudo-objects and all methods as pseudo-classes
</dt>
<dd class="dd">Stack frames of are of type <code class="ph codeph">packageName.className.methodName(Signature)ReturnType</code> extending <code class="ph codeph"><method></code>codeph> representing the method being executed,
of size the stack frame size, with source file and line number via fields and a name resolver,
and all methods are pseudo-classes of type <code class="ph codeph"><method type></code> of size based on the JITted and byte code sizes. The method sizes are then not part of the class size.
<p class="p">This can be useful to find out which methods have large JITted or byte code sizes. They can be viewed by going to the histogram view,
then selecting <code class="ph codeph"><method type></code> and listing objects.
</p>
</dd>
</dl>
</dd>
<dt class="dt dlterm">
<span class="ph menucascade"><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">DTFJ Parser</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Suppress Class native memory size calculations (IBM system dumps)</span></span>
</dt>
<dd class="dd">
By default, when MAT parses IBM system dumps, the size of classes includes some of the amount of native memory in the Java process (but outside of the Java heap) which is related to those classes such as native memory for bytecode and JIT compiled code for the class methods. Check this option to disable this calculation and only report Java heap usage.
</dd>
<dt class="dt dlterm" id="task_configure_mat__hprof_preferences">
<span class="ph menucascade"><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">HPROF Parser</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Parser Strictness</span></span>
</dt>
<dd class="dd">
By default, the HPROF parser runs in strict mode. This means that
any deviation in the file from the
<a class="xref" href="http://java.net/downloads/heap-snapshot/hprof-binary-format.html" target="_blank">HPROF specification</a>
is treated as a severe error, an exception is thrown, and dump
processing stops. There is one exception to this rule which is
that we can reliably workaround the observed issue in
<a class="xref" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=404679" target="_blank">bug #404679</a>
.
<p class="p">This
is a change in behavior from previous
releases when a
warning
was
shown in the error log and processing
continued. This
default
change was made to alert the user to a
potential problem
either
with the file itself or a bug in the JVM
or in MAT. You may
choose
to change the strictness of the parser:</p>
<dl class="dl">
<dt class="dt dlterm">Strict
</dt>
<dd class="dd">Default. Any deviation from the HPROF specification causes
an exception to be thrown and processing to stop (with the
exception of
<a class="xref" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=404679" target="_blank">bug #404679</a>
.) This option may be specified on the
command line with -DhprofStrictnessStop=true
</dd>
<dt class="dt dlterm">Warning
</dt>
<dd class="dd">
Choose this option to revert to the old behavior where a
warning is printed to the error log and processing continues.
This option is not recommended because the warning is probably
a sign of a problem. Please open a bug report instead. This
option may be specified on the
command line with
-DhprofStrictnessWarning=true
</dd>
</dl>
</dd>
<dt class="dt dlterm">
<span class="ph menucascade"><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">HPROF Parser</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Include additional references from class objects
found in a HPROF file.</span></span>
</dt>
<dd class="dd">
Class objects have hidden references to the other objects.
These include the signers and the protection domain.
Memory Analyzer can include them via pseudo-fields named
<span class="keyword parmname"><signers></span> and <span class="keyword parmname"><protectionDomain></span>.
Sometimes it might be useful to see these references, and this
option allows that.
</dd>
<dt class="dt dlterm">
<span class="ph menucascade"><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">HPROF Parser</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Stack frames</span></span>
</dt>
<dd class="dd">
Normally stack frames are just shown in the Thread overview and stacks query.
This option allows stack frames to be treated as objects which are then visible like any other Java object in a Memory Analyzer view.
<dl class="dl">
<dt class="dt dlterm">Normal
</dt>
<dd class="dd">Stack frames are just shown in the Thread overview and stacks query.
</dd>
<dt class="dt dlterm">Only stack frames as pseudo-objects
</dt>
<dd class="dd">
Stack frames are of type <code class="ph codeph"><stack frame></code>, size 0, with method names and source file
and line numbers via fields and a name resolver.
<p class="p">This is useful when looking at paths to and from objects via local variables as the stack frames are visible in
the paths to GC roots queries.</p>
</dd>
<dt class="dt dlterm">Stack frames as pseudo-objects and running methods as pseudo-classes
</dt>
<dd class="dd">Stack frames of are of type <code class="ph codeph">packageName.className.methodName(Signature)ReturnType</code> extending <code class="ph codeph"><method></code> representing the method being executed,
of size an estimate of the stack frame size, with source file and line number via fields and a name resolver,
and those methods are pseudo-classes of type <code class="ph codeph"><method type></code> of size 0.
The size of a stack frame is estimated as 8 bytes times the maximum number of object references from a frame of that type.
<p class="p">This can be useful to find out which methods are currently running and how much stack space they take up.
To examine running methods then take the histogram view, filter by '\(', then sort by instances or instance size.
</p>
</dd>
</dl>
</dd>
<dt class="dt dlterm">
<span class="ph menucascade"><span class="ph uicontrol">General</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Appearance</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Colors and Fonts</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">OQL comment color</span></span>
</dt>
<dd class="dd">Modify the color of comments in the Object Query Language (OQL) studio.</dd>
<dt class="dt dlterm">
<span class="ph menucascade"><span class="ph uicontrol">General</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Appearance</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Colors and Fonts</span><abbr title="and then"> > </abbr><span class="ph uicontrol">Memory Analyzer</span><abbr title="and then"> > </abbr><span class="ph uicontrol">OQL keyword color</span></span>
</dt>
<dd class="dd">Modify the color of keywords in the Object Query Language (OQL) studio.</dd>
</dl>
</div>
</div>
</div>
</body>
</html>