After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 511218 - nautilus segfault starts using large percentage of cpu
nautilus segfault starts using large percentage of cpu
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-22 10:19 UTC by Mark Thiele
Modified: 2008-06-13 09:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Mark Thiele 2008-01-22 10:19:59 UTC
Please describe the problem:
Nautilus starts using a large percentage of the cpu and writing a constant nautilus-debug-log.txt with line after line of "debug log dumped due to signal 11"
I have not been able to isolate the cause of the problem or deliberately trigger it. It seems to start on login and continue throughout the session. I have witnessed the problem on four computers (a dell inspiron notebook, two acer desktops and an old Aptiva desktop) all running Ubuntu Gutsy.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
This bug seems to appear in different distros and is well reported across the web.
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/153382
http://www.linuxquestions.org/questions/linux-software-2/an-interesting-nautilus-problem-core-dumped-due-to-signal-11.-over-and-over-again-607277/
http://linuxmint.com/forum/viewtopic.php?f=18&t=7125&p=44967
http://ubuntuforums.org/archive/index.php/t-461530.html
http://forums.gentoo.org/viewtopic-t-632081.html?sid=d94a03351876b39c58f72685fb924e07
http://forum.mandriva.com/viewtopic.php?t=78149&sid=fe306e160f243870ccbd1fa69f4f14c9
http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/2007-November/039406.html

Hope that this is useful.
Comment 1 Gilles Dartiguelongue 2008-05-08 15:05:41 UTC
Our gentoo downstream bug report is:

https://bugs.gentoo.org/show_bug.cgi?id=208224

Pacho made a patch to stop using the 'setup_debug_log_signals' but we'd like to get some upstream thoughts on this issue.
Comment 2 A. Walton 2008-05-08 15:43:48 UTC
Pretty sure we disabled this a few months ago in trunk when there were some problems with this.

2007-12-17  Alexander Larsson  <alexl@redhat.com>

        * src/nautilus-main.c:
        (setup_debug_log_signals):
	Disable unsafe segv handler by default

Might not have made it back to the stable branch (2.20).
Comment 3 Pacho Ramos 2008-05-09 09:19:03 UTC
For me seems that problems gone (on 2.20) after removing all old thumbnails in homedirs. I haven't still tested in 2.22, but I remember that disabling sgv handler in 2.20 worked (and also removing thumbnails even keeping it enabled).

Feel free to close this if you want (and original reporters are ok)

Thanks
Comment 4 Cosimo Cecchi 2008-06-13 09:12:32 UTC
Yes, that code seems to have been disabled in SVN trunk for a while.
Closing as FIXED, please feel free to reopen the bug if there's still something wrong. Thanks!