Firefox becomes unresponsive when savings images

[Benjamin Kerensa]

What: Whenever I save images or download any files Firefox becomes temporarily unresponsive and gvfsd-metadata soars to 90% CPU consumption.

Expected: Not insane use of CPU and unresponsiveness

Steps to reproduce:

1. Launch firefox
2. Go to any site with images and right click save
3. Firefox becomes unresponsive
4. Run top from cli and see gvfsd-metadata consuming tons of CPU

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: firefox 19.0.2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bkerensa 2284 F.... pulseaudio
BuildID: 20130308124351
Channel: Unavailable
Date: Fri Apr 5 16:29:29 2013
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-18 (169 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.141 metric 9
MarkForUpload: True
PrefSources:
 prefs.js
 [Profile]/<email address hidden>/defaults/preferences/defaults.js
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351 (In use)
RelatedPackageVersions:
 google-talkplugin 3.17.0.0-1
 totem-mozilla 3.6.3-0ubuntu4
 rhythmbox-mozilla 2.98-0ubuntu3
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to raring on 2012-11-24 (132 days ago)
dmi.bios.date: 06/24/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0VK06J
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA00:bd06/24/2011:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0VK06J:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System Inspiron N411Z
dmi.sys.vendor: Dell Inc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Garrett (garrett-redhat-bugs)]

Description of problem:
Go to a website, right click on a link to a posted file, select "save link as" It's many seconds before the dialog box appears for choosing a destination.

Version-Release number of selected component (if applicable):
firefox-20.0-1.fc18.i686

Additional info:
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1165252

[Garrett Mitchener (garrett-mitchener)]

I'm seeing something very much link this on Fedora 18. I may not be seeing exactly the same thing, but when I use "save link as" there's a delay of many seconds before the dialog box appears asking where to save it. This is with Firefox 20.0. I'm posting here and at https://bugzilla.redhat.com/show_bug.cgi?id=957391

[rakkenes (sverre-rakkenes)]

when I use ff now on raring, I can not rightclick and save images at all.. has it been disabled?

[Benjamin Kerensa (bkerensa)]

I ran a stacktrace and can see some odd messages in it right around when the unresponsiveness occurs and also I noticed in the stacktrace it seems to be looking for some libraries that are not found?

[Benjamin Kerensa (bkerensa)]

I ran a stacktrace and can see some odd messages in it right around when the unresponsiveness occurs and also I noticed in the stacktrace it seems to be looking for some libraries that are not found?

[Benjamin Kerensa (bkerensa)]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130516012338

Steps to reproduce:

Try to save files or images

Actual results:

Firefox becomes unresponsive for 1 to 2 minutes

Expected results:

Files save without unresponsiveness

[Benjamin Kerensa (bkerensa)]

This is apparently occuring in multiple Linux Distros including Ubuntu and Fedora and we have a confirmed bug open downstream in Ubuntu that has stacktrace and other info that would be helpful in addressing the bug.

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1165252

[Benjamin Kerensa (bkerensa)]

Reported upstream

[Alice0775 (alice0775)]

If you cannot reproduce in Aurora23.0a2 and Nightly24.0a1,
this is duplication of Bug 860213

[Simona-marcu (simona-marcu)]

Benjamin, please can you confirm whether this issue still occurs on the latest Nightly and on the latest Aurora?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/

[Simona-marcu (simona-marcu)]

Setting the resolution of this bug to Resolved Incomplete. If anyone is still able to reproduce or has more information to provide, please change the status back.

[Scrapmachines (scrapmachines)]

I can still see this bug in latest nightly. When I download an image of around 1 MB size, after downloading, firefox will hang for a moment. I think this bug will be fixed once the saving is done in a separate thread, but I am not sure.

[Fedora (fedora-redhat-bugs)]

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

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.

[Fedora (fedora-redhat-bugs)]

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Vseerror (vseerror)]

stacktrace with firefox symbols would be great https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report

[Benjamin Kerensa (bkerensa)]

There is already a stack trace in the downstream bugs on Launchpad and Red Hat's Bugzilla. Are you familiar with upstream reporting?

[Vseerror (vseerror)]

(In reply to Benjamin Kerensa [:bkerensa] from comment #7)
> There is already a stack trace in the downstream bugs on Launchpad and Red
> Hat's Bugzilla. Are you familiar with upstream reporting?

Sure. I didn't notice.
Since you reported both, do you still see this problem?

[Benjamin Kerensa (bkerensa)]

I dont use that version of Ubuntu anymore this was in 2013 so thats six Ubuntu releases back. Chris Coulson or someone from the Ubuntu Mozilla Team should confirm since this is a downstream bug thats marked confirmed still.

Their bug squad would mark it invalid if it was no longer present. Either way Mozilla does not invest much time in Linux stability and fixes.

[Paul White (paulw2u)]

Further to comment #17, reporter not in a position to reproduce
Upstream issue closed "RESOLVED WORKSFORME" on 2017-01-12
Cannot reproduce here with Firefox 64 and Ubuntu 18.04
No comments for almost 4 years so closing