Quote:

Thanks for the update! Searching and replying in morph.zone works again.

Quote:

Thanks, unfortunaletly I will have to revert to the former one : Wayfarer 8.3 stalls without any reason when trying to load websites. It cannot be closed and even Ambient menus wont't appear (to reboot the PowerMac). Ambient is frozen.

[ Edité par K-L 17.05.2024 - 08:37 ]

@K-L: As I found out on my system (G5), it depends on other, parallel running or shortly closed programs, before starting Wayfarer. In some cases Wayfarer crashes or show this described behaviour. (but tis was at previous versions of Wayfarer the same).
Following programs mostly influences Wayfarer: OWB, ImageFX, Pagestream (not allways), HD-Record, and some others. All of them is one property common: they need a lot of RAM! I guess that they don't have a clean RAM-management.

My experience: Wayfarer 8.3, started on a fresh bootet system, is very stable. If you start above mentioned progs after Wayfarer has come up, it does'nt influence Wayfarer (maybe one of those progs will crash then...but not Wayfarer)

@K-L

Please open Wayfarer's Settings and go to Network and set HTTP/2 to Disabled. Let me know if this makes a difference.

Quote:

Thanks, it did the trick :)

8.4 out to address the HTTP/2 problem.

https://wayfarer.icu not reachable!

load from here: https://www.morphos-storage.net/dl.php?id=2132748

@jacadcaps

With 8.4 it comes Error Message to load a Website:

Quote:

This Error Message comes on 4 of 5 Websites.

thanks for all
little problem 'cannot connect to server'
i have to close and open wayfarer

Quote:

Thanks. Unfortunately, the problem still exists even if I disable HTTP2 suport. For example : https://www.meteo-lyon.net

There is also a new problem, mentionned by others : on a regular basis, we get "cannot connect to server".

[ Edité par K-L 19.05.2024 - 16:30 ]

Same here!

Same here, lots of "cannot connect to server" messages.
Couldn't even login to Morphzone with Wayfarer
.

Reach different servers: Needs also disabled HTTP/2-support to work!

Edit: Does'nt work allways .... after some pages loaded, same error occours...

[ Editiert durch Amigaharry2 19.05.2024 - 21:09 ]

Interesting. This has not shown up in my tests. I'll try to fix this in a couple of days.

I'm back to using v7.8 currently, as v8.x seems to be more trouble than it's worth using, or actually sitting and waiting while nothing happens for most of the time, with either the CPU running at full speed while the page and the whole browser is "frozen in time"!

There ought to be some way to interrupt any webpage/JavaScript (tab) and either pause or halt/kill it whenever it causes more trouble than it offers the experience it is supposed to. I can't even get Task Manager to launch to send a "Break" to Wayfarer to stop it (wasting CPU cycles doing nothing) as the JavaScript has a stranglehold on the system, which should just not be possible.

Quote:

No, there isn't.

A modern OS on modern hardware can run each browser tab as a separate, isolated process - there's a UI process, a network process and then each browser tab has a separate web process where the JavaScript runs. But those modern OS cannot "interrupt" JavaScript, either. Best they can do is to kill the offending (busylooping) process entirely and start a new one and re-load the page there.

And if you're wondering why this isn't the case on MorphOS - run TaskManager on Windows and see how much RAM each web process of Chrome needs. That'd be even worse on MorphOS (add 50-60MB per process). Not to mention you have to have an RPC (inter-process communication) to make this all work which means serializing and deserializing everything passing between the UI / Network / Web processes. That's a additional CPU burden, simply offset by the fact that CPUs other than PPC have advanced quite considerably while the best MorphOS CPU is now >20 years old.

You think Wayfarer takes a while to start? Imagine each new tab would take this long with the 1 tab per process approach.

[ Edited by jacadcaps 20.05.2024 - 20:04 ]

Run at task pri -1?

8.5 out now, should fix the network-related problems of 8.3/4.

@Georg

You can try using -1 on AROS once you're done porting https://github.com/jacadcaps/webkitty

Quote:

Impressive jaca, muchos gracias!!

edit: still a lot of not connect (error 7), but weirdly random now


[ Edited by Stevo 20.05.2024 - 22:26 ]

Thanks for your great support jaca!

@ jacadcaps - as analogkid said - Thanks for your great support.

I only said there ought to be a way to stop JavaScript whenever it was necessary to do so, but I never thought it was possible with MorphOS . . . sadly !

These "Couldn't connect to server" messages still appear if I use a SOCKS5 proxy. I was using one because it was said that it brings a better network performance. Is this still viable?

Randomly same problem as before! After loading 2 or 3 different pages this error comes again! At this point no page can beload - Wayfarer has to be quit. I don't use a proxy. Does'nt make any difference whether http/2 support is on or off.

Edit:
When switching http/2 support it loads again, but ofter some pages the same. Switching back http/2 it loads again and the game newly starts....

[ Editiert durch Amigaharry2 21.05.2024 - 08:38 ]

Quote:

the correct spanish phrase is "muchas gracias" not "muchos gracias".
But yes, thank you Jacaps for this new update,there's less left to catch up with Firefox.