Bug 821282
| Summary: | [abrt] xscreensaver-base-5.15-3.fc16: kill: Process /usr/bin/xscreensaver was killed by signal 6 (SIGABRT) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aurelio Calegari <aureliocalegari> | ||||||||||
| Component: | xscreensaver | Assignee: | Mamoru TASAKA <mtasaka> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 16 | CC: | mtasaka | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:e336f2cfad7ed8940e0eadc624173eabd87fda78 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-05-17 01:01:29 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Aurelio Calegari
2012-05-13 22:41:52 UTC
Created attachment 584186 [details]
File: event_log
Created attachment 584187 [details]
File: backtrace
Created attachment 584188 [details]
File: coredump
Created attachment 584189 [details]
File: maps
Would you know how many processes were running when this crash happened? (or maybe are many processes running even now?) Or would you have some idea about under what circumstance this issue occurred? The reason I am asking this is that it seems that calling fork from xscreensaver process failed because of EAGAIN, usually this is because there are too many processes. Yes, there were too many process, they all crashed: - I had two eclipse instances running (each in different workspaces) - OC4J container running - Evolution was opened - Thunar (SVN) - A number of terminals - A number of Dolphins (file manager) - Gedit - Pidgen What had crashed when I was back: -Both eclipses -Oc4J -Thunar -Evolution -Screen saver (unlocked my computer) But note: It's 8GB quad core box, and it should cope very well with the above. I run the same sort of load in my MacOSX 10.7 and also in WinXP and don't have this problem. Sorry, I forgot to mention, I also had Chrome and Firefox open, each with a number of tabs. Both crashed too. Well, if issues like that you mentioned on comment 7 is reproducible, seeing processes by - ps auwwx - pstree may show some clues what is the real culprit (or maybe it was just too many applications were running)... (In reply to comment #7) > But note: It's 8GB quad core box, and it should cope very well with the above. Well, the maximum number of processes is usually not related with the capacity of your machine (nowadays), but is determined by the (default) settings of kernel and OS (Fedora). You can see the current value by $ ulimit -u (or $ ulimit -a will show the same information with some explanation). [aurelica@its27940 home]$ ulimit -u 1024 [aurelica@its27940 home]$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63597 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 1024 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited So, that means I had more than 1024 processes running? (In reply to comment #10) > So, that means I had more than 1024 processes running? Currently I believe so. Maybe one of the applications you were using created many threads or created many zombie processes. After some discussion with Red Hat security responsible team and the upstream, I decided to once close this bug as WONTFIX. Thank you for reporting anyway. |