On Tue, 27 Apr 2010 11:09:32 +0100 Rik Griffin <[email protected]> wrote:
> In message <[email protected]> > Rob Kendrick <[email protected]> wrote: > > > > I've CCed the netsurf-dev list with this, as it might be interesting > > for the non-RISC OS developers, as an insight into restrictions we > > have to keep in mind if we want to continue supporting RISC OS. I > > hope you don't mind. > > One partial solution springs to mind for all this - use more dynamic > areas. Say one area per page, then when when Netsurf discard the > page, destroy the DA as well. Maybe extra DAs for cached content as > well? The trouble here is that there are loads of pieces of data, handled by vastly different pieces of code, and some of these pieces of data are shared between pages. (String internment springs to mind. Also, do we share identical images with identical URLs which happen to appear on more than one open page?) Also, it'd complicate all the code that allocates memory quite significantly. Is it worth trying to put the wapcaplet strings in their own DA anyway? We also toyed once with keeping bitmaps in their own DA. Could that easily be shoe-horned in with modifications only to riscos/bitmap.c ? B.
