@Gregor

I don't recall if there is an option to disable it completly. You can switch to "Document Viewer" mode instead of "Document Browser" or "Primary Web Browser". In "Document Viewer" mode the caches (memory and disk) are the smallest.

@hotrod

The mininum supported configuration for Odyssey 3.0 under AROS 64-bit is 2GB RAM. My tests show that with having 2-3 tabs opened and browsing mostly amiga-friendly sites + Discord, the RAM usage stabilized around that number.

Keep in mind that Odyssey 3.0 on AROS 64-bit is pre-configured to use larger caches as simply RAM is not a limiting factor here. Having JavaScript JIT also consumes some additional RAM, probably in the range of 0.5GB.

In order to cut the caches to minumum you can change the Cache Model setting in Odyssey preferences from "Primary Web Browser" to "Document Viewer".

Finally it is quite possible that Wayfarer has a smarter way to manage caches when memory consumpion reaches hardware limit. There is nothing stopping this from being implemented in Odyssey, because Odyssey 3.0 is using the public part of Waywarer 3.0 codebase already.

@samo79Quote:

2.0 and 2.1 were released for AROS with WebKit 2.24.

3.0 is rebased to WebKit 2.34.6 + Wayfarer 3 changes. Odyssey major version will match Wayfarer's major version to have a good point of reference.

Update of the engine caused a number of regressions in the browser UI, but I don't see anything that can't be fixed or is a show stopper.

Odyssey is currently rebased to webkitgtk 2.24.4 which is close enough to Wayfarer branch 1.x (webkitgtk 2.30) to allow porting functionality (BE patches?) from that branch.

If anyone is interested in trying to compile this version, please get in touch with me.