Clicking on huge image locks/hangs machine (complete loss of interactivity)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
xorg (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Note that whilst I've initially filed this against Firefox, it is a wider cross-stack performance issue (a single application should not be able to bring the machine down). Clicking on the following image:
http://
sets the Firefox title, but then immediately locks the machine with all loss of interactivity.
Ideally Firefox should not undertake activities that are likely to bring the machine down (such as allocated huge arrays for data that it has not yet even received) and ideally the rest of the stack down to the kernel should not let a single application bring the rest down.
(Metadata and a tiled-image viewer for the image can be found at: http://
summary: |
- Clicking on huge image brings machine to standstill (complete loss of + Clicking on huge image locks/hangs machine (complete loss of interactivity) |
description: | updated |
Changed in firefox (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
tags: | added: review-request |
Changed in xorg (Ubuntu): | |
status: | Invalid → New |
status: | New → Incomplete |
I need to look at this in more detail, but it seems that it's creating a lot of X resources when opening that image, and Xorg ends up using GBs of RAM