Closed Bug 1476850 Opened 7 years ago Closed 6 years ago

Saving small file or image freezes UI

Categories

(Toolkit :: Downloads API, defect)

Product:
Toolkit
Component:
Downloads API
Version:
61 Branch
Platform:
Unspecified
Windows 10
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: makedir, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce: 1. Go to twitter (or other sites) 2. save a picture to disk 3. you cant interact with the page (for example like, or zoom another image => JS) until the image is finished saved to disk (appears in download manger as finished) Actual results: You cannot interact any JS ajax actions until Firefox has finished saved the file to disk. You cannot right click too nor do anything in Firefox in this frozen time window. It seems to be related to just smaller files, like an image. If it is a larger file, then the manager just starts to download it. But if it is just an image, like 200kb in size, it seems the start download+create file+finish file is causing some short freeze period, in which the entire browser is not reacting. Expected results: Still can interact with page.
Component: Untriaged → Widget: Win32
OS: Unspecified → Windows 10
Product: Firefox → Core
Component: Widget: Win32 → Downloads API
Product: Core → Toolkit

The priority flag is not set for this bug.
:mak, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mak77)

We'd need a performance profile to make this actionable, as it is there isn't much we can do. I cannot reproduce the problem on my Windows 10 system. Maybe it's just related to disk I/O exhaustion.

A performance profile can be generated following the procedure at https://profiler.firefox.com

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mak77)
Resolution: --- → INCOMPLETE

The issue isnt that easy to reproduce. I kinda think it is somehow related to Twitter, and the fact that there is some Javascript running on the main thread blocking the UI of Firefox. This just happens if you scroll down Twitter for a long time, and there is lot of Twitter loaded on the time line. The longer you scroll down, the longer the freeze is.

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