Description of problem: System has been freezing up lately; I could see that all my RAM was being used, and when I checked "All Processes" (rather than "My Processes") I could see that abrt-action-lis was taking up 1GB or RAM. This has happened a few times during the last week and I have to reboot to recover. Version-Release number of selected component (if applicable): 2.1.12-2 How reproducible: Happens daily(?) Steps to Reproduce: 1.Wait until you notice the system slowing down 2.Check RAM usage and proccesses 3. Actual results: abrt using way too much RAM Expected results: abrt not using so much RAM Additional info:
The most recent issue showing in abrt is: mate-panel killed by SIGSEGV This occurred about half an hour before I was forced to reboot in the most recent instance. It says that it "cannot be reported" because "The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out."
Same thing happened again just now ... When I hover over the "abrt-action-lis" process in System Monitor, it says: /usr/bin/python -u /usr/bin/abrt-action-list-dsos -m maps -o dso_list This time it got up to 1.5GiB and then teetered back and forth between 1.5 and 1.4 GiB. I had to use kill -9 kill -15 was not enough For the record, abrt never pops up a notification regarding the crash. I opened abrt manually while this was going on and it had registered a crash for gnote this time about 30 minutes prior. after killing the runaway process, I went back into abrt and the gnote crash was no longer there.
Thank you for the report. Could you please attach 'maps' file from the dump directory. All dump directories are placed in '/var/tmp/abrt'.
Created attachment 872708 [details] "maps" file from the /var/tmp/abrt dump directory Recall that the crash information disappears from abrt after killing the runaway process; there was no dump directory available for the previous crash. So I caused another crash and retrieved the "maps" file (attached) prior killing the runaway process. The dump directory was deleted after I killed the runaway process.
Thanks! If you have time to install the following scratch build and re-test, please do so and report the results here. http://koji.fedoraproject.org/koji/taskinfo?taskID=6617760
Sorry for slow response -- been a little busy ... Is that build the same as all the abrt updates that just came in through the normal updates repository? If so, the updated packages do not address the issue....
I am no longer able to reproduce the issue ... It was 100% reproducible before and so far 100% unreproducible now ... I'm not sure what the issue was, but the only significant change I am aware of on my computer between before and now is that I addressed an error I was getting while using yum -- the error message started with: "error: rpmdbNextIterator: skipping h" -- I addressed it by deleting __db.001 - __db.003 and then running rpm --rebuilddb