Odyssey 3.0 alpha - bug reports coming slowly...

PS: unfortunataly, the bug with loading and saving scripts is not fixed. After a restart, the scripts has vanished.

@Primax

No launcher because it is useless since it starts in few seconds. Why you need the launcher back?
I will try to add an installer as soon as possible.

@afxgroup

Tested on X1000.

www.iltalehti.fi seems to work mostly (if not fully even).
www.veikkaus.fi made the OS to try to flush all memory and memory pools and freezing the whole machine eventually.

@afxgroup

Also me for Launcher reintroducing

cool. much better than the last version.
still some open issues for sure.
well done!

regards...
michael

Great job Andrea! Thanks for sticking with this huge project!
I hope you can keep at it! Donation sent!

I installed the clib from archive into LIBS: and I was testing
v310 on a number of sites while running it in RAM: on my X5K/20
with 2GB RAM.

It loaded & indexed the fonts very quickly. It loaded Amiga
sites (like here) quickly and without any issues.

While I never had any visits from the Grim Reaper, I tried a
number of other sites...

Your github page came back as empty.

I tried to load https://www.washingtonpost.com but while most of
the text appeared, no pictures and then everything came to
a freeze. Fortunately, I could quick reboot.

After reboot, I tried that site with next to nothing else
running, with the same results. Could one single webpage
seriously consume more than 1.2GB of RAM??? ...or is it some
javascript running wild?

Then I tried my bank, same thing. I tried Goggles, but had to
spoof as Safari to get any results to appear. Then I tried
YouTube but it also froze with memory loss.

Like I said, I never got a crash. In some tests I was able to
quit the browser with no complaints, but it rarely freed more
than 20% of the memory it consumed.

So it all makes me wonder, if something rabidly eating the
memory, do you think it can be curtailed in the future? If it's
retarded website caching the entire contents of their site in
the browser, are there any tricks that can be done impede that?

I really look forward to your work on this and you have my best
wishes for success!!

Thanks again!

PJS