You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This uses a utility class providing static methods to create new buffers directly and bypassing the pooling mechanism. The user must also release the allocated buffers.</p>
1411
+
</div>
1412
+
<divclass="admonitionblock note">
1413
+
<table>
1414
+
<tr>
1415
+
<tdclass="icon">
1416
+
<iclass="fa icon-note" title="Note"></i>
1417
+
</td>
1418
+
<tdclass="content">
1419
+
<divclass="paragraph">
1420
+
<p>It has been <ahref="https://github.com/quarkusio/quarkus/issues/50538">reported</a> that some libraries using the <code>UnpooledByteBufAllocator</code> might not release some heap buffers. This will not decrement the reported allocation even if memory is no longer reserved. This might lead to astronomical values in reported memory.</p>
<p>If high allocation values are reported, there are 2 ways to determine whether it’s a real memory leak:</p>
1431
+
</div>
1432
+
<divclass="ulist">
1433
+
<ul>
1434
+
<li>
1435
+
<p>By enabling <ahref="https://netty.io/wiki/reference-counted-objects.html#leak-detection-levels">leak detection</a>, as documented by Netty. Example:</p>
<p>Inspect a memory dump from the application.</p>
1448
+
</li>
1449
+
</ul>
1450
+
</div>
1451
+
</div>
1407
1452
</div>
1408
1453
<divclass="sect2">
1409
1454
<h3id="quarkus-extensions-using-micrometer"><aclass="anchor" href="#quarkus-extensions-using-micrometer"></a>List of Quarkus core extensions automatically instrumented with Micrometer</h3>
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</span>
226
+
</p>
227
+
228
+
</div>
229
+
<divclass="card-footer">
230
+
<divclass="icons">
231
+
232
+
<ahref="https://github.com/quarkusio/quarkus/discussions/42116" title="See the working group proposal"><i
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</span>
560
-
</p>
561
-
562
-
</div>
563
-
<divclass="card-footer">
564
-
<divclass="icons">
565
-
566
-
<ahref="https://github.com/quarkusio/quarkus/discussions/42116" title="See the working group proposal"><i
0 commit comments