Bug 683279 - [abrt] nautilus-2.30.1-6.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.30.1-6.fc13: Process /usr/bin/nautilus was killed by signal...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:30c860d5456f7fc7b51c40273c7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 00:10 UTC by Wendell Baker
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 12:02:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (41.88 KB, text/plain)
2011-03-09 00:10 UTC, Wendell Baker
no flags Details

Description Wendell Baker 2011-03-09 00:10:19 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus --sm-client-id 1010eaf64f6a8dd0f9128356862072663400000265000049 --sm-client-state-file /home/wbaker/.config/session-state/nautilus-1297050625.state
component: nautilus
crash_function: nautilus_window_get_active_slot
executable: /usr/bin/nautilus
kernel: 2.6.34.7-56.fc13.i686.PAE
package: nautilus-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1299626511
uid: 500

comment
-----
This report is about nautilus crashing.  The rest is color.

This is not reproducible but is a symptom of being logged in for many days and weeks.


The nm-applet grows without bounds and sooner or later exhausts memory.
The workaround is to kill & restart it.


Nautilus seems to grow as well, but it crashes frequently enough that it doesn't hang onto its "lost" memory for long enough to cause problems.



After the incident settled out, the big things on my machine are:

In the output of ps, field ten (10) is the "size"

$ ps -lef | sort -n -k 10
 S wbaker   25484 12176  1  80   0 - 70211 poll_s 15:33 ?        00:00:14 nautilus --sm-client-id 1010eaf64f6a8dd0f9128356862072663400000265000049 --sm-client-state-file /home/wbaker/.config/session-state/nautilus-1297050625.state
0 S wbaker   12831     1  0  80   0 - 74410 poll_s Feb06 ?        00:00:55 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=42
0 S wbaker   12471 12176  0  80   0 - 78503 poll_s Feb06 ?        00:33:53 pidgin --session 101a37ab86d252c6d812812973279051400000023010055 --display :0.0
0 S wbaker   12409 12176  0  80   0 - 98804 poll_s Feb06 ?        00:19:01 gnome-panel --sm-client-id 1010eaf64f6a8dd0f9128356862071974500000265000048
0 S wbaker   12827     1  0  80   0 - 124129 poll_s Feb06 ?       01:50:31 /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=27
0 S wbaker   19445 19434  0  80   0 - 215792 poll_s Mar06 ?       00:12:20 /usr/lib/openoffice.org3/program/scalc.bin -calc file:///borg/bakers/somefile.ods
0 S wbaker    8957     1  0  80   0 - 226268 poll_s Feb10 ?       02:21:50 /usr/bin/python /usr/bin/gwibber
0 S wbaker   12365 12348 16  80   0 - 307084 poll_s 11:13 ?       00:45:35 /usr/lib/firefox-3.6/firefox
0 S wbaker   30667 30663  7  80   0 - 442219 poll_s Mar04 ?       06:26:06 /usr/lib/thunderbird-3.1/thunderbird-bin
0 S wbaker   20426     1  0  80   0 - 534168 poll_s Feb07 ?       00:15:22 gnucash

How to reproduce
-----
... the disk is running constantly and intermittently ; lots of pressure on memory

1. nautilus
2. nm-applet is on the panel
3. doing various work
4. sftp://USER/Administration/Stuff   (sftp into another account on another machine)
5. drag & drop a pdf file

... now the disk runs constantly.   swapping, kcryptd constantly running.  The load is 6+ and the machine is unuseable.

nm-applet is ~2+ GB (it has a known? core leak)

... kill that, restart that ...

... the disk is still running ... nautilus still isn't redrawing on the desktop or in a window

nautilus is 800MB 

... see the crash...

Comment 1 Wendell Baker 2011-03-09 00:10:22 UTC
Created attachment 483070 [details]
File: backtrace

Comment 2 Bug Zapper 2011-05-30 11:04:06 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2011-06-27 12:02:44 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.


Note You need to log in before you can comment on or make changes to this bug.