On Sun, Oct 14, 2012 at 01:29:33PM +0100, Martin Bazley wrote:
> The thing which is *really* annoying about using NetSurf on a USB drive
> is the enormous amount of time it takes to quit - up to thirty seconds
> on a bad day! This seems to be dependent on the amount of browsing done
> beforehand. I've tried cleaning out the cookies and turning off history
> collection, and that made it slightly better, but that can't be all of
> it.
Get an OS with a better IO layer :)
> The last time I examined NetSurf's log file after quitting I saw that
> the lines which were taking up the vast majority of the time since the
> quit request was received were a set of repeated calls to
> bitmap_save_file(bitmap) in riscos/bitmap.c. This seems to be the result
> of the following loop in bitmap_quit():
>
> void bitmap_quit(void)
> {
> struct bitmap *bitmap;
>
> for (bitmap = bitmap_head; bitmap; bitmap = bitmap->next)
> if ((bitmap->state & BITMAP_PERSISTENT) &&
> ((bitmap->state & BITMAP_MODIFIED) ||
> (bitmap->filename[0] == '\0')))
> bitmap_save_file(bitmap);
> }
>
> I'm at a loss to understand exactly what 'bitmaps' NetSurf could have
> 'modified' in the course of the session, or where it's 'saving' them to.
> All I know is that this is a horrendously inefficient operation!
They're probably the webpage thumbnails used in the history viewer. It
might be nice to have an option to disable this.
But NetSurf is not being inefficient here; RISC OS is.
B.
