There was much discussion about a year ago about the cache performance on
RISC OS, and there were some code changes, but I would like to add the
results of some investigations of the Netsurf v3.4 cache on my Iyonix,
running RISC OS 5.23 (11 Oct 2015).
In the past I had problems with the cache taking large amounts of disc
space, and the resulting long backup times for !Boot, so my current
settings are 10MB space, expiring after 2 days.
However, the actual space usage was 45MB (as measured by Filer Count),
and it contained 210 files. What was more difficult to find was that
there were 7,298 directories with 8 levels, which occupied another 14MB,
of which 6,412 contained no files at any lower level. So only 886
directories actually contained the 210 files of cached data. Enumeration
of the cache took about 2 minutes.
I decided to delete all 6,412 directories that contained no data, saving
about 12MB of disc space. More importantly, counting or enumerating all
the cache now takes about 7 seconds. There are still the same number of
files and cached bytes.
Netsurf itself still seems to work, but I have not noticed any change in
So, some questions:
- When are cached files deleted to meet the configured size & expiry?
- Are directories included in the space used?
- Are directories ever deleted? If so, when?
- Will deletion of empty directories cause any problems for Netsurf?
I have looked at the help ... but that says that files are not deleted by
Netsurf, and makes no mention of directories. It also refers to a
'Perform maintenance' button which can be used to delete redundant files
... but this is nowhere to be seen!
Does Netsurf not save its hotlist and history till the user quits the
Last night I was looking for tips on how to use CSS for something on
my website, came across a wonderful site and immediately added it to
my Netsurf hotlist. An hour later, some other application froze and
the computer had to be rebooted.
Today I wanted to return to that site about CSS, but there was no
record of it in my hotlist. Nor in my history. Tried all sorts of
searches via Google and Duckduck -- no luck. Bereft.
Is there any way to make Netsurf save history and hotlist during a
session? Or am I misunderstanding something?
As for the site I lost, maybe somebody else knows it and could point
me in the right direction.
- Exceptionally clean design. The bits of code within sentences were
presented with a grey background.
- Fine use of language, not cutesy or nerdy or commercial.
- It had a surprisingly nifty name, one syllable I think, almost in
the league of web.com or code.com -- so simple it made me wonder that
the writers found it still available.
- Further surprise when I got to a deeper page: it was a UK company,
despite the ".com" domain, located somewhere like Shoreditch or
Stop press: Found it! It's html.com
Back to original Q about when Netsurf saves its hotlist.
Jim Nagel www.archivemag.co.uk
The Atari Freemint OS moved to github and they posted this link to
When I open it with NS, it downloads about 14k in about 3-4mins but
then shows the error below and crashes out.
Failure when receiving data from the peer
render/html_object.c:127: html_object_callback: Assertion `c->base.status != CONTENT_STATUS_ERROR' failed.
As previously stated the cocoa frontend has been disabled in the CI
and any build errors in this frontend are no longer considered to
"break the build"
Unless a maintainer for cocoa comes forward and fixes it so it
compiles and runs before the next developer weekend in June this
frontend will be removed from the source at that time.
I'm sure I raised a feature request for this a long time ago but I
can't see it. Anyway, is it possible to get .m3u style playlists to
play automatically on NetSurf? Oregano does this but with NS you have
to save the playlist and then launch it. I have the following MimeMap
entries for m3u:
audio/m3u MPEGURL aa7
audio/x-mpegurl MPEGURL aa7 .m3u
Richard Porter http://www.minijem.plus.com/
Skype: minijem2 mailto:email@example.com
I don't want a "user experience" - I just want stuff that works.
As a frequent user of the Atari NS build I passed on your comments
to the Freemint (OS) mailing list.
I don't pretend to know much about the toolchain but they have asked
for some more details about what the issues are ?
My hope is that they may be able to investigate and improve things.
The Freemint OS recently moved onto Github.
> Date: Mon, 6 Feb 2017 11:25:25 +0000
> From: Vincent Sanders <vince(a)netsurf-browser.org>
> Subject: Frontend maintainership
> To: netsurf-dev(a)netsurf-browser.org, netsurf-users(a)netsurf-browser.org
> At the recent NetSurf developer weekend we discussed many topics
> one of which was our regular review of the frontends.
> atari - The atari frontend is built for m68k and coldfire variants
> using a variant of the netsurf cross compliation
> toolchain/sdk. No serious updates have been made to this
> toolchain in some time and it has become a burden.
> Unless this is addressed before the next developer weekend the
> frontend will be disabled in the CI and subsequently code
At the recent NetSurf developer weekend we discussed many topics
one of which was our regular review of the frontends.
Except for Amiga and GTK none of the frontends have a active maintainer.
The cocoa and atari frontends are however causing a great deal of concern.
cocoa - Unless a maintainer can be found (or at least someone willing
to fix it) before 11th Febuarary 2017 the CI for this target
will be disabled. The code will be removed during the next
developer weekend on the 10th June.
This decision has been made because the effort to keep this
frontend building is large and we have many reports that the
resulting binary simply crashes when started.
atari - The atari frontend is built for m68k and coldfire variants
using a variant of the netsurf cross compliation
toolchain/sdk. No serious updates have been made to this
toolchain in some time and it has become a burden.
Unless this is addressed before the next developer weekend the
frontend will be disabled in the CI and subsequently code
riscos - Still lacks a full time maintainer but due to its userbase
the team keeps it working. Gets a reprieve again and will be
reconsidered next time.
windows - Lacks a full maintainer but has been fixed up to be at least
useful. A maintainer for this frontend would be welcome.
amiga - Chris Young continues to provide excellent maintainership no
monkey - test frontend is useful and we envisage expanding the scope
of its usage.
beos - The Beos port is generally only tested on Haiku at this
point. The frontend is kept useful by mmu man and
pulkomandy. Main issues revolve around the CI slave and its
crashy java port.
gtk - Vince looks after this and despite gtk+ changing API a lot it
framebuffer - generally good shape but the Linux framebuffer and input
need attention. It has been agreed we will look into
using libinput to improve this area.