Red Hat Bugzilla – Bug 869076
[abrt] apg-2.3.0b-16.fc17: check_pass: Process /usr/bin/apg was killed by signal 6 (SIGABRT)
Last modified: 2013-08-01 13:35:33 EDT
Description of problem:
Run APG from command line with basic options, checking against dictionary file with 19,697,684 lines (possible too many lines in file?).
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: apg -a 0 -m 10 -t -r master.txt
:Thread no. 1 (1 frames)
: #5 check_pass at restrict.c:93
Created attachment 631774 [details]
Created attachment 631775 [details]
Created attachment 631776 [details]
Created attachment 631777 [details]
Created attachment 631778 [details]
Created attachment 631779 [details]
Created attachment 631780 [details]
Created attachment 631781 [details]
Created attachment 631782 [details]
It looks like it may have been unable to allocate enough memory to handle your dictionary.
Does it work on smaller ones?
How much memory + swap do you have? If you add more does it complete?
Ran some basic tests: dictionary files of 100,000; 500,000; and 1,000,000 lines completed successfully, but test of 1,500,000 caused the abrt. Physical resources are 8GB RAM and just a shade under 10GB swap, and not in a position to allocate more physical resources (nothing available on hand).
Well, not sure what we can do here. apg is likely not very memory efficent, but if you run out of memory, I'd just advise using a smaller set ?
You could ask upstream to improve memory handling, but there has not been an apg release in about 9.5 years, so I don't know how much luck you will have there.
I suppose one other work around would be to tweak /proc/sys/vm/overcommit_memory...
echo 1 > /proc/sys/vm/overcommit_memory
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.