873871 - Firefox becomes unresponsive when saving images or files

Status: RESOLVED WORKSFORME

(Firefox :: Downloads Panel, defect)

Description

[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

Comment 1

[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

Comment 2

[Alice0775 White]

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

Comment 3

[Simona Badau, Desktop QA]

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/

Comment 4

[Simona Badau, Desktop QA]

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.

Comment 5

[Girish Sharma [:Optimizer]]

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.

Comment 6

[Wayne Mery (:wsmwk)]

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

Comment 7

[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?

Comment 8

[Wayne Mery (:wsmwk)]

(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?

Comment 9

[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.

Comment 10

[Wayne Mery (:wsmwk)]

optimizer, does this still reproduce for you?

Comment 11

[Girish Sharma [:Optimizer]]

The system on which i was facing this problem was work laptop and the problem was getting just too frequent to use Nightly at all, so I disabled e10s. I do not plan to enable it again in near future as well.

Comment 12

[Wayne Mery (:wsmwk)]

Thanks for the update.  Much has changed in 2 years and I don't see e10s mentioned in any earlier comments, so changing status to => incmplete

Comment 13

[Girish Sharma [:Optimizer]]

Oh damn. I guess I commented on wrong bug. nevertheless, yeah I haven't seen this exact bug since ages.

Comment 14

[Wayne Mery (:wsmwk)]

In that case, WFM unless ben comes  back with something different.
(And note, the downstream bug hasn't budged, and not likely to move IMO)