this is per a discussion that we had re: malloc failures and such - the idea being that if we're running out of memory, we'll start doing things like skipping images and other memory-hungry activities.
Reporter: can you clarify what exactly is wrong? What Mozilla should do that it doesn't do? http://www.mozilla.org/quality/bug-writing-guidelines.html
we are creating a version of mozilla named minimo that will run on extremely constrained small devices. through some research on browsers for these kind of devices we have found that one feature they have is to gracefully handle situations that can exhaust all the available memory. in such case the browser on these devices detect a low memory situation and then inform the user that the page can not be displayed, or the full contents of the page can not be displayed. this bug is to a similar feature to the minimo version of mozilla.
moving minimo bugs to the new bugzilla product.
Component: Browser-General → General
Product: Browser → Minimo
Target Milestone: Future → ---
Version: Trunk → unspecified
Assignee: dougt → nobody
Component: General → General
Product: Minimo → Core
Summary: [minimo] handle loading large pages with low physical memory → handle loading large pages with low physical memory
there are a number of other bugs on this subject, going to close this one out
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.