Description of problem: Since upgrading to Fedora 8 sporadically a nautilus process starts consuming a lot of CPU time and is continuously writing the line "(USER): debug log dumped due to signal 11" to the file nautilus-debug-log.txt in the user's home directory. I'm marking this bug urgent as on our multi-user system a number of these runaway processes severly impact the system's performance. Version-Release number of selected component (if applicable): nautilus-2.20.0-6.fc8 nautilus-cd-burner-2.20.0-1.fc8 nautilus-debuginfo-2.20.0-6.fc8 nautilus-extensions-2.20.0-6.fc8 nautilus-sendto-0.12-5.fc8 How reproducible: I don't know why the nautilus processes segfault, but when they do they should not start using all the available CPU time. Steps to Reproduce: 1. 2. 3. Actual results: Nautilus process starts consuming a lot of CPU time and is continuously writing the line "(USER): debug log dumped due to signal 11" to the file nautilus-debug-log.txt in the user's home directory. Expected results: Write a single line to the file nautilus-debug-log.txt and exit. Additional info: - Attached backtrace created with gdb. - The external bug reference contains a number of references to other bug reports of the same problem on various distributions. According to https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/153382 just a few days ago a fix has been released for Hardy.
Created attachment 293043 [details] gdb backtrace of running nautilus process
Created attachment 293044 [details] gdb backtrace of another running nautilus process
Master bug from Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/150471 Proposed patch: http://launchpadlibrarian.net/12083923/92_from_svn_no_buggy_signal_handler.patch
nautilus-2.20.0-8.fc8 has been submitted as an update for Fedora 8
Thanks for the new nautilus packages. Today I installed them on the system having showing this problem and for the coming week I'll see what effect it has.
nautilus-2.20.0-8.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.