https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-06-30T15:32:31ZpfSense bugtrackerpfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=548182021-06-30T15:32:31ZJim Pingle
<ul></ul><p>Could be partially mitigated by <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a> -- That daemon should be made optional and off by default except for the few people who need its capabilities for PKCS#11.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=548202021-06-30T15:33:48ZJim Pingle
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/11933">Todo #11933</a>: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional</i> added</li></ul> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=548872021-07-04T13:26:52ZMarcos M
<ul></ul><p>Here are some stats on various 21.05 VMs:</p>
<ul>
<li>Uptime: 6d2h</li>
<li>RAM: 1G</li>
<li>pcscd usage: 326M</li>
<li>2 VTI IPsec tunnels</li>
</ul>
<pre>
last pid: 11696; load averages: 1.32, 0.95, 0.89 up 6+02:41:39 13:14:03
66 processes: 1 running, 65 sleeping
CPU: 0.0% user, 0.0% nice, 0.0% system, 0.8% interrupt, 99.2% idle
Mem: 58M Active, 398M Inact, 223M Wired, 100M Buf, 257M Free
Swap: 410M Total, 410M Free
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
7702 root 5 20 0 326M 320M select 3:51 0.02% pcscd
70890 root 1 20 0 103M 38M getblk 0:00 0.00% php-cgi
85503 root 1 52 0 103M 36M accept 0:00 0.00% php-fpm
15450 root 1 52 0 103M 38M accept 0:01 0.00% php-fpm
</pre>
<ul>
<li>Uptime: 11d16h</li>
<li>RAM: 1G</li>
<li>pcscd usage: 620M</li>
<li>No IPsec tunnels</li>
</ul>
<pre>
last pid: 51378; load averages: 0.38, 0.55, 0.57 up 11+16:07:38 13:13:21
54 processes: 1 running, 53 sleeping
CPU: 2.7% user, 3.8% nice, 13.7% system, 0.0% interrupt, 79.8% idle
Mem: 30M Active, 246M Inact, 355M Laundry, 210M Wired, 136K Buf, 89M Free
ARC: 71M Total, 40M MFU, 26M MRU, 1573K Anon, 564K Header, 3446K Other
38M Compressed, 95M Uncompressed, 2.50:1 Ratio
Swap: 2048M Total, 192M Used, 1856M Free, 9% Inuse
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
7648 root 3 20 0 620M 496M select 7:19 0.05% pcscd
352 root 1 52 0 131M 28M accept 1:06 0.00% php-fpm
1716 root 1 52 0 103M 28M accept 0:21 0.00% php-fpm
46386 root 1 52 0 103M 27M accept 0:15 0.00% php-fpm
</pre>
<ul>
<li>Uptime: 5d17h</li>
<li>RAM: 8G</li>
<li>pcscd usage: 312M</li>
<li>No IPsec tunnels</li>
</ul>
<pre>
last pid: 29474; load averages: 0.50, 0.39, 0.30 up 5+17:21:00 13:23:51
69 processes: 2 running, 67 sleeping
CPU: 2.9% user, 0.0% nice, 2.9% system, 0.0% interrupt, 94.1% idle
Mem: 61M Active, 547M Inact, 897M Wired, 240K Buf, 6391M Free
ARC: 340M Total, 106M MFU, 224M MRU, 1344K Anon, 1224K Header, 7573K Other
93M Compressed, 268M Uncompressed, 2.87:1 Ratio
Swap: 2048M Total, 2048M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
13305 root 3 20 0 312M 301M select 3 3:26 0.02% pcscd
6196 unbound 4 20 0 149M 79M kqread 2 2:08 0.31% unbound
355 root 1 52 0 135M 48M accept 3 0:29 1.19% php-fpm
356 root 1 20 0 135M 48M piperd 0 0:24 0.33% php-fpm
</pre> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=548892021-07-04T14:32:22ZMarcos M
<ul></ul><p>Additional note:</p>
<p>Stopping the service while IPsec is in use leads to the following log spam:<br /><pre>
Jul 4 14:21:28 charon 11632 02[CFG] C_GetSlotInfo failed: SLOT_ID_INVALID
Jul 4 14:21:28 charon 11632 02[CFG] error in C_WaitForSlotEvent: GENERAL_ERROR
</pre></p>
<p>This ends up causing continuous log rotation in very short periods which leads to quickly growing disk usage and 100% CPU usage.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=552682021-07-27T10:59:32ZSteve Y
<ul></ul><blockquote>
<p>There looks to be a limit at ~1GB</p>
</blockquote>
<p>If you meant a limit for pcscd's RAM usage, I pulled up a few...a 3100 (21.05) is at 960 MB and a couple of 4860s just over 1000, but our lone 2.5.2 has almost 2 GB:</p>
<pre><code>PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND<br /> 7457 root 3 20 0 1946M 1929M select 1 22:00 0.00% pcscd</code></pre>
<p>That's with uptime 18 days. On all four, the dashboard shows memory usage % that is lower than even just the pcscd process.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=555202021-08-06T17:07:49ZSean M
<ul><li><strong>File</strong> <a href="/attachments/3805">clipboard-202108061650-gdclv.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3805/clipboard-202108061650-gdclv.png">clipboard-202108061650-gdclv.png</a> added</li></ul><p>I haven't run into this issue before but just today I noticed swap usage at 100% and memory was very high, turns out pcscd had leaked and consumed the memory.</p>
<p>Currently on: <br />21.05-RELEASE (amd64)<br />FreeBSD 12.2-STABLE</p>
<p><img src="https://redmine.pfsense.org/attachments/download/3805/clipboard-202108061650-gdclv.png" alt="" /></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=556002021-08-10T12:47:51ZAlexander Arques
<ul></ul><p>Just registered to report the same issue. I have never used smart cards or IPSec tunnels and today I noticed all swap space was used up and RAM usage was at 80%, turns out the pcscd daemon was using more than 1GB of memory.</p>
<p>Running:<br />2.5.2-RELEASE (amd64)<br />built on Fri Jul 02 15:33:00 EDT 2021<br />FreeBSD 12.2-STABLE</p>
<p>Uptime: 34 days</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=559352021-08-25T16:10:29ZMichael Smith
<ul><li><strong>File</strong> <a href="/attachments/3837">clipboard-202108251709-me8di.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3837/clipboard-202108251709-me8di.png">clipboard-202108251709-me8di.png</a> added</li></ul><p>Can confirm the bug on my system. Was a clean upgrade from the last version.<br />2.5.2-RELEASE (amd64)<br />built on Fri Jul 02 15:33:00 EDT 2021<br />FreeBSD 12.2-STABLE</p>
<p><img src="https://redmine.pfsense.org/attachments/download/3837/clipboard-202108251709-me8di.png" alt="" /></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=559362021-08-26T06:32:12ZUwe Dippel
<ul></ul><p>Same-same. 7 days of uptime, over night it ramped up and killed DNS ('no space left'). 2.5.2-RELEASE (amd64) clean install. Though, the culprit is well-known. <br />To me, priority of 'normal' is questionable since my users reported 'the internet is down'. No dig @pfsense. Just restarted the service and noticed the horrendous memory usage. Disabled pcscd and immediately everything was back to normal.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=559372021-08-26T07:12:36ZJim Pingle
<ul></ul><p>Uwe Dippel wrote in <a href="#note-9">#note-9</a>:</p>
<blockquote>
<p>Same-same. 7 days of uptime, over night it ramped up and killed DNS ('no space left'). 2.5.2-RELEASE (amd64) clean install. Though, the culprit is well-known. <br />To me, priority of 'normal' is questionable since my users reported 'the internet is down'. No dig @pfsense. Just restarted the service and noticed the horrendous memory usage. Disabled pcscd and immediately everything was back to normal.</p>
</blockquote>
<p>We agree that it's a sizable problem, but the main reason it's set to "normal" is because the service is disabled by default now (See <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a> ) and very few people need to enable it. It's only necessary for those who need to use PKCS#11 Smart Cards for certificates. We have not seen any reports that the memory leak happens when pcscd is latched onto actual hardware, so it's possible that this isn't an issue for those who actively use the daemon. It's also possible that there are no reports because not enough people use it yet to notice.</p>
<p>Either way, the problem resides in the daemon which we do not control, so it would need to be fixed upstream, hence our focus on a more practical workaround/mitigation.</p>
<p>Until the next release which includes the changes from <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a> you can add the main commit on that issue as a system patch to disable the pcscd service (See <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933#note-7">#11933#note-7</a> )</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=560552021-08-26T23:09:33ZCharles Ng
<ul></ul><p>I see the same log spam as described in <a class="external" href="https://redmine.pfsense.org/issues/12095#note-4">https://redmine.pfsense.org/issues/12095#note-4</a> if pcscd is stopped.</p>
<p>The log rotation bzip2 processes consume all the CPU cycles.<br /><pre>
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 3328 16.1 0.9 18244 9512 - R 21:59 4:28.92 bzip2 -f /var/log/ipsec.log.0
root 487 15.8 0.9 18244 9500 - R 22:06 3:10.48 bzip2 -f /var/log/ipsec.log.6
root 28366 15.8 0.9 18244 9504 - R 22:01 3:59.19 bzip2 -f /var/log/ipsec.log.6
root 88479 15.6 0.9 18244 9504 - R 21:58 4:43.51 bzip2 -f /var/log/ipsec.log.4
root 80103 15.5 0.9 18244 9504 - R 21:57 4:52.81 bzip2 -f /var/log/ipsec.log.3
root 99250 15.1 0.9 18208 9460 - R 22:33 0:06.21 bzip2 -f /var/log/ipsec.log.0
root 55746 14.9 0.9 18244 9504 - R 22:03 3:39.07 bzip2 -f /var/log/ipsec.log.3
root 86455 14.9 0.9 18244 9500 - R 22:05 3:12.95 bzip2 -f /var/log/ipsec.log.5
root 50899 14.6 0.9 18244 9504 - R 22:02 3:47.29 bzip2 -f /var/log/ipsec.log.2
root 75157 14.6 0.9 18244 9504 - R 22:04 3:29.48 bzip2 -f /var/log/ipsec.log.4
root 27619 14.1 0.9 18244 9504 - R 22:00 4:09.67 bzip2 -f /var/log/ipsec.log.1
root 20617 13.6 0.9 18244 9504 - R 22:00 4:15.34 bzip2 -f /var/log/ipsec.log.5
</pre></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=560562021-08-27T07:20:35ZJim Pingle
<ul></ul><p>Charles Ng wrote in <a href="#note-11">#note-11</a>:</p>
<blockquote>
<p>I see the same log spam as described in <a class="external" href="https://redmine.pfsense.org/issues/12095#note-4">https://redmine.pfsense.org/issues/12095#note-4</a> if pcscd is stopped.</p>
</blockquote>
<p>That is known and expected. Do not just stop the service if you have IPsec enabled. Read my previous comment for a link to a viable workaround.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=562192021-09-06T16:49:23ZBug Reporter
<ul></ul><p>Just found out where 1.3GiB of my free memory went. Returned to normal as soon as I killed the pcscd.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=563442021-09-11T02:30:53ZPhilip Cook
<ul></ul><p>This memory leak is rather problematic. <br />2.5.2-RELEASE (amd64) <br />Uptime 64 Days 22 Hours 02 Minutes 06 Seconds</p>
<pre>
last pid: 891; load averages: 0.90, 0.77, 0.78 up 64+22:00:17 02:18:37
76 processes: 1 running, 75 sleeping
CPU: 2.3% user, 0.0% nice, 1.2% system, 0.5% interrupt, 96.0% idle
Mem: 2264M Active, 2039M Inact, 2227M Laundry, 1019M Wired, 554M Buf, 273M Free
Swap: 4096M Total, 2159M Used, 1937M Free, 52% Inuse
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
9896 root 3 20 0 4557M 2389M select 4 54:08 0.04% pcscd
</pre> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=563592021-09-11T22:03:23ZMarcos M
<ul></ul><p>Philip Cook wrote in <a href="#note-14">#note-14</a>:</p>
<blockquote>
<p>This memory leak is rather problematic. <br />2.5.2-RELEASE (amd64) <br />Uptime 64 Days 22 Hours 02 Minutes 06 Seconds</p>
<p>[...]</p>
</blockquote>
<p>See JimP's comments <a class="external" href="https://redmine.pfsense.org/issues/12095#note-10">https://redmine.pfsense.org/issues/12095#note-10</a></p>
<p>You can apply the patch that disables it when not needed to avoid the issue.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=573562021-11-10T14:48:35ZPhil K
<ul></ul><p>The same happened to me today. I realized it when I started receiving e-mails with lines like<br /><pre>
bzip2: I/O or other error, bailing out. Possible reason follows.
bzip2: No such file or directory
Input file = /var/log/ipsec.log.23, output file = /var/log/ipsec.log.23.bz2
newsyslog: `/usr/bin/bzip2 -f /var/log/ipsec.log.23' terminated with a non-zero status (1)
</pre></p>
<p>Apparently, this is caused by the high CPU load and bzip2 processes taking a long time to compress logfiles (I found <a class="external" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200741">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200741</a> about this. Seems to be another (unresolved?) issue).</p>
<p>Anyway, all of a sudden I was in a situation in which pcscd had been killed, not by me but by the kernel due to it consuming too much memory (<code>Nov 10 18:15:01 neptun kernel: pid 7452 (pcscd), jid 0, uid 0, was killed: out of swap space</code>) and then, the log spam kicked in.</p>
<p>I tried both manually restarting the pcscd and applying the patch mentioned in <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a>, but couldn't stop it. I ended up restarting the pfSense, hoping that it would work. As this specific instance's only connection to the Internet is through an IPSec tunnel it felt a bit risky restarting it if there is an IPSec related issue.</p>
<p>Would there have been any other way to stop the log spam? I suppose this could be helpful for others that experience the same issue.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=574022021-11-14T07:26:07ZPedro Ribeiro
<ul></ul><p>I politely disagree with the assigned priority for this bug, particularly given that a CE release is likely months away. Initially I hit the problem with pcscd leaking memory on two pfSense boxes yesterday, with the first sign being no DNS due to unbound having been killed, probably due to out-of-memory conditions, so then I disabled pcscd on both boxes. But the next day I stumbled upon high CPU usage on both boxes, with difficulty to get both the web interface/ssh responding. In case it helps anyone, here are the steps I used to regain control.</p>
<p>1. I applied the patch <code>afcc0e9c97c1993ae6b95f886665fcb4375d26c7</code> as suggested.<br />2. Stopped and started the IPSec service (charon) as clicking restart didn't seem to make a difference at all.<br />3. Meanwhile syslog continued misbehaving. I had to kill bzip2 from the command line several times while doing the next steps.<br />4. Cleared all logs.<br />5. Importantly, I changed the compression for log retention on purpose, as given the text <em>WARNING: Changing this value will remove previously rotated compressed log files!</em> I figured this would be exactly what I needed, kill any log rotation given the issue with bzip2.</p>
<p>The issue with syslog/bzip2 on its own seems intriguing. One would expect that disabling a service - whatever it may be - wouldn't have catastrophic consequences in terms of repeated, unbounded logging, eventually maxing out the CPU, which makes regaining control of a box challenging.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=574112021-11-15T08:15:16ZJim Pingle
<ul></ul><p>The problems you're hitting are a mix of somewhat but not really related things.</p>
<p>This issue being the memory leak itself, which is beyond our control, hence the other issues we have made to work around it. The workarounds are on <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a> and have already been implemented in the code base, but have not yet been included in a release. The next release will be coming sometime in the few months ahead. The snapshots are quite stable if people want to run them (in a lab first to test).</p>
<p>Pedro Ribeiro wrote in <a href="#note-17">#note-17</a>:</p>
<blockquote>
<p>1. I applied the patch <code>afcc0e9c97c1993ae6b95f886665fcb4375d26c7</code> as suggested.<br />2. Stopped and started the IPSec service (charon) as clicking restart didn't seem to make a difference at all.</p>
</blockquote>
<p>The best thing to do there is reboot after applying the patch. Though some have seen that pressing Save on the advanced settings tab in IPsec is sufficient, it's safest to reboot. The discussion around that should stay on <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: PC/SC Smart Card Daemon ``pcscd`` running on all devices at all times, should be optional (Resolved)" href="https://redmine.pfsense.org/issues/11933">#11933</a> and not here as it isn't relevant to the memory leak, but the changes we have made to control pcscd.</p>
<blockquote>
<p>3. Meanwhile syslog continued misbehaving. I had to kill bzip2 from the command line several times while doing the next steps.</p>
</blockquote>
<p>This is because IPsec is logging like crazy because it can't communicate with the (stopped) pcscd daemon which its configuration still references at that point, since applying the patch doesn't do anything but adjust the code. The daemon configuration needs to be refreshed. We have another separate issue for this in <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Stopping IPsec daemon on the Status / Services page lead to log files flooding if pcscd daemon is... (Resolved)" href="https://redmine.pfsense.org/issues/12468">#12468</a> so going forward the daemons are stopped and started together properly if/when pcscd is enabled.</p>
<blockquote>
<p>5. Importantly, I changed the compression for log retention on purpose, as given the text <em>WARNING: Changing this value will remove previously rotated compressed log files!</em> I figured this would be exactly what I needed, kill any log rotation given the issue with bzip2.</p>
</blockquote>
<p>Sort of, but it depends on what is causing it. The problem again is the high rate of logging at the time. Disabling compression can help there since compression will bog down the log rotation process but syslogd itself will still be taking quite a bit of load. It also doesn't kill the backlog of existing bzip2 processes. See <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Disable log compression on new installations when ``/var/log`` is a ZFS dataset with compression ... (Closed)" href="https://redmine.pfsense.org/issues/12011">#12011</a> for more there.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=575002021-11-22T05:38:39ZViktor Gurov
<ul></ul><p>pcscd bugreport:<br /><a class="external" href="https://github.com/LudovicRousseau/PCSC/issues/55">https://github.com/LudovicRousseau/PCSC/issues/55</a></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=582362022-01-09T18:16:36ZSimon Quigley
<ul></ul><p>Not sure there's a lot of value in my post, if this service has now been set to disabled by default..</p>
<p>I just wanted to report that my pfsense instance was throwing a lot of errors related to swap in the kernel log, and when I looked, this daemon was eating 15G of the 16G of ram in my box.<br /><pre><code class="shell syntaxhl">
ast pid: 72748<span class="p">;</span> load averages: 0.56, 0.41, 0.50 up 143+06:16:53 18:57:54
216 processes: 1 running, 215 sleeping
CPU: 4.5% user, 0.3% <span class="nb">nice</span>, 1.7% system, 0.2% interrupt, 93.4% idle
Mem: 455M Active, 1906M Inact, 11G Laundry, 2010M Wired, 1540M Buf, 468M Free
Swap: 4096M Total, 4088M Used, 8260K Free, 99% Inuse
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
39410 root 1 52 0 133M 32M accept 3 0:39 0.59% php-fpm
85739 root 1 52 0 133M 32M accept 3 0:46 0.10% php-fpm
66234 root 1 52 0 133M 32M accept 1 0:38 0.10% php-fpm
61691 root 3 20 0 15G 11G <span class="k">select </span>2 217:40 0.00% pcscd
</code></pre></p>
<p>Which is pretty horrendous. I stopped the service, and I will disable it, until I'm able to upgrade and reboot.</p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=584442022-01-20T10:25:36ZMr Sparkles
<ul><li><strong>File</strong> <a href="/attachments/4008">PFsence memory leak.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4008/PFsence%20memory%20leak.png">PFsence memory leak.png</a> added</li><li><strong>File</strong> <a href="/attachments/4009">PFsence memory leak2.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4009/PFsence%20memory%20leak2.png">PFsence memory leak2.png</a> added</li></ul><p>This may be redundant information, just mentioning that this mem leak is not only an issue on lower memory systems.</p>
<p>System: <br />2.5.2-RELEASE (amd64)<br />built on Fri Jul 02 15:33:00 EDT 2021<br />FreeBSD 12.2-STABLE</p>
<p>Uptime: 16 days</p>
<p><img src="https://redmine.pfsense.org/attachments/download/4008/PFsence%20memory%20leak.png" alt="" /><br /><img src="https://redmine.pfsense.org/attachments/download/4009/PFsence%20memory%20leak2.png" alt="" /></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=616232022-06-01T13:01:34Z→ luckman212luke.hamburg@gmail.com
<ul></ul><p>Update: looks like the PCSC maintainer has fixed the mem leak: <a class="external" href="https://github.com/LudovicRousseau/PCSC/issues/55#issuecomment-1143815658">https://github.com/LudovicRousseau/PCSC/issues/55#issuecomment-1143815658</a></p> pfSense - Bug #12095: Memory leak in pcscdhttps://redmine.pfsense.org/issues/12095?journal_id=650372023-01-05T09:42:44ZJim Pingle
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-11 priority-4 priority-default closed" href="/issues/13826">Feature #13826</a>: Update pcsc-lite</i> added</li></ul>