Why do all AmigOS 4.1 browsers crash on WinUAE?

Small pages work IBrowse, Netsurf, OWB.
But larger pages fail.

which machine? and which pagese are you trying to load? remember that our browser are ancient and doesn't supports a lot of web sites. And new web sites eat a lot of memory too..

@newton

That has not been my experience. On my X5000 large sites might not render correctly but generally it does not crash.

Can you give an example site?

Cheers,
Bill "tekmage" Borsari

Check out Amiwest.net

@Newton

Keep an eye on the memory usage, and CPU usage, it can tell you something,
how web page looks depends on web browser how old web engine is.

if computer is slow, there are things you can do to lower CPU usage, you can disable anti-aliased fonts, for example.

if your running low on ram, then open the web browser on 16bit screen, instead of running it on 32bit screen, this should cut memory usage in half.

Put your temp files on a hard drive, if you are using IBrowse, if your computer has not a lots of memory.

Some web browsers use data types, a bad datatype can crash the system. Did you install something just before crashing started? (Snoopy / SoopDOS can tell you something about what system components that are used.)

It can be hardware related, or hardware dependent. Its know that A1222 has problems with virtual memory for now, can be fixed latter.

Delete the font cache, a broken font, can crash the system.
and run fix fonts, if you have installed new fonts.

@Newton

Unfortunately with the state of Amiga brosers currently, there
are a number of points of failure with a lot of websites that
want to load the internet in each webpage...

Blame lazy brainless web coders.

Be that as it may, IBrowse tends to auger through the page code
as well as it can, can get hung up on complicated JS and can
cause crashes when a site send boatloads of oversized images
consuming all the gfx memory.

Oddity... err... Odyssey gets a lot further with some >HTML4
page layout but the JS stuff often does not render/work,
persistent scripts won't die (google) or memory errors trash the
system.

All in all, most times the page that crashes or won't render at
all in IB these days, I find Odd doesn't get a passably better
job done either.

In some cases you can tweak the per site settings in IBrowse
to turn off JS or image loading, if you can get by with the
rest of the page that gets though.

Unfortunately, web browsing is a rough landscape for Amigas
these days. At least this all means most of the spyware
coursing through every vein of your peecee is DOA.

Good luck,

PJS

Generally Amiga OS is hobby OS. I use Netsurf 99% of time as it best compromise of speed, stability and compatibility. If I need to do something serious, I just use my Win machine.

@Newton

Hi Newton,

It is important to tell us what kind of system you are using.

Are you running AmigaOS 4.1 on AmigaOne hardware or emulation using WinUAE?

In theory it should not matter, but some modern websites require lots of RAM. If your host system has limited amount of RAM, it may not have enough RAM to run Windows + WinUAE + AmigaOS 4.1 + web browser + view very large web pages.

My ancient OS4 system also bogs down on very large web pages.

It is a Micro-AmigaOne with PPC 750 GX CPU and 256 MB of RAM.

That is a tiny amount of RAM compared to what comes with the modern OS4 systems.

For web surfing ...

I use IBrowse 3.0a for most of the Amiga friendly websites.

I use Origyn Web Browser 3.31 for amiga.org.

NetSurf 3.11 works well for me as an alternative to IBrowse.

Odyssey Web Browser 1.23 r5 (Jan 2 2022) generally works ok, but sometimes I get error messages about RAM allocation and then Odyssey kind of locks up.

AWEB APL 3.5.12 still works for some Amiga friendly websites.

Anyways ... Please give us more details.

Cheers,
redfox