- From: Charles Pritchard <chuck@jumis.com>
- Date: Mon, 27 Sep 2010 16:44:11 -0700
On 9/27/10 3:30 PM, Rob Evans wrote: > > I think one of the most useful things that a js script could know is > how much memory is available and how much the current page is using. > I'm writing a js game engine and knowing how much I can safely site in > memory would be incredibly useful! > > On 27 Sep 2010 23:19, "timeless" <timeless at gmail.com > <mailto:timeless at gmail.com>> wrote: >> >> what exactly do you intend to do if you get such a signal? >> >> In general, this is mostly a user problem. There are two basic cases: >> 1. user has one constrained device with one browser accessing a single >> web site (yours) with no other open applications. >> 2. user has a device with multiple open windows (various sites, >> various applications). >> I'm just talking about the bare minimum: sending a simple event window.dispatchEvent(lowmemory) No details / guarantees. It's just a hint. Mozilla has made efforts to handle low memory issues (allocation errors or otherwise) mainly in the handling of image resources. I'd like to see the practice become more widespread. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100927/4674508b/attachment.htm>
Received on Monday, 27 September 2010 16:44:11 UTC