+++ This bug was initially created as a clone of Bug #1166613 +++ The problem is in setroubleshoot server or maybe in python garbage collector. Here is the test case scenario: * setroubleshoot server is bombarded by 4 AVCs per second (always the same access) * "ps --no-headers -o uid,size,vsize -C setroubleshootd" is executed 120 times, 1 second pause after each run 0 31404 270008 0 115244 360592 0 115512 362192 0 115376 362056 0 115640 362320 0 115908 362588 0 116308 362988 0 116576 363256 0 116572 363252 0 117148 363828 0 117280 363960 0 117548 364228 0 117812 364492 0 117808 364488 0 118236 364916 0 118632 365312 0 118496 365176 0 119192 365872 0 119188 365868 0 119460 366140 0 120136 366816 0 120532 367212 0 121104 367784 0 120968 367648 0 121368 368048 0 121636 368316 0 122224 368904 0 122620 369300 0 123080 369760 0 123076 369756 0 123476 370156 0 124200 370880 0 124196 370876 0 124332 371012 0 124600 371280 0 124996 371676 0 125260 371940 0 125256 371936 0 125796 372476 0 126060 372740 0 126656 373336 0 126788 373468 0 127184 373864 0 127772 374452 0 128168 374848 0 128592 375272 0 128588 375268 0 128856 375536 0 128852 375532 0 129120 375800 0 129668 376348 0 129932 376612 0 130496 377176 0 130896 377576 0 131584 378264 0 131980 378660 0 132528 379208 0 132524 379204 0 132920 379600 0 133636 380316 0 134304 380984 0 134836 381516 0 135536 382216 0 135532 382212 0 136220 382900 0 136744 383424 0 137596 384276 0 138416 385096 0 139112 385792 0 139640 386320 0 140456 387136 0 141024 387704 0 141020 387700 0 141288 387968 0 141284 387964 0 141420 388100 0 141988 388668 0 142124 388804 0 142120 388800 0 142680 389360 0 142948 389628 0 143348 390028 0 143344 390024 0 143780 390460 0 143776 390456 0 144048 390728 0 144616 391296 0 144612 391292 0 144880 391560 0 144876 391556 0 145280 391960 0 145724 392404 0 145992 392672 0 145988 392668 0 146580 393260 0 146848 393528 0 147248 393928 0 147880 394560 0 148280 394960 0 148140 394820 0 148884 395564 0 148880 395560 0 149692 396372 0 149688 396368 0 149964 396644 0 150788 397468 0 151188 397868 0 151904 398584 0 152612 399292 0 152876 399556 0 153140 399820 0 153572 400252 0 153840 400520 0 154640 401320 0 154644 401324 0 154908 401588 0 155464 402144 0 155600 402280 0 155864 402544 0 155860 402540 0 156424 403104 0 156560 403240 0 156956 403636 0 156952 403632 0 157356 404036 0 158224 404904 0 158224 404904 0 158920 405600 0 158916 405596 0 159320 406000 0 159872 406552 0 160268 406948 0 161096 407776 0 161496 408176 0 162196 408876 0 162760 409440 0 162756 409436 0 163288 409968 0 163840 410520 0 164240 410920 0 164936 411616 0 165336 412016 0 165784 412464 0 166044 412724 0 166184 412864 0 166728 413408 0 166724 413404 0 166992 413672 0 167256 413936 I see similar numbers on following architectures: ppc64, s390x, x86_64. This also affects Fedora. It appears to be a memory leak in setroubleshootd.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.