On 30/08/14 10:42, Steve Fryatt wrote:
> I think it's worth adding that the "many other apps [which] manage to
> release their DAs when documents are closed", referred to by Chris,
> are almost certainly using some kind of sliding block heap (such as
> the ubiquitous flexlib for C) to manage their
On 30 Aug, Michael Drake wrote in message
<54010c15.8040...@netsurf-browser.org>:
> So that's how NetSurf deals with memory. On RISC OS you have a further
> issue. NetSurf uses UnixLib, which implements the memory allocation stuff
> using DAs. If a DA contains contents 1, 2 and 3, and they
On 29/08/14 23:05, cj wrote:
> I think this problem has been raised on a number of occasions,
> probably for more than a year. The comment that has come back is that
> RISC OS has appalling memory management routines and not much can be
> done. Many other apps manage to release their DAs when do
In article <5400c022.3000...@netsurf-browser.org>,
Michael Drake wrote:
> You say "persist" and "still"; is there some context for this that
> I am missing? Do we have a log files for such runs?
I think this problem has been raised on a number of occasions,
probably for more than a year. The
On 29/08/14 16:53, m...@johnwoodhouse.plus.com wrote:
> the problem seems to persist
You say "persist" and "still"; is there some context for this that I am
missing? Do we have a log files for such runs?
If there isn't one for this already, please open a bug report[1] with
the relevant detail
I have been using NS 3.0 for the most part, but having tried with 3.1 and
now the latest available 3.3 (Dev CI #2070), the problem seems to persist:
Using VARPC, memory is limited - the most I can use is around 102Mb. and
running Netsurf initially knocks that back to c. 94Mb with a Google default
