Problem whit Ibrowse

[futaura]

It is most likely a particular website that is causing IBrowse to crash.  When IBrowse crashes, if you try to load the same site after a reboot, and it still crashes, then obviously that would confirm it.  AFAIK, IB2.4 will be crash free - there are almost too many bugfixes to count.

However, how many connections have you told IBrowse to use? This is important because you mention MiamiDx and ADSL.  MiamiDx (and Miami) actually have a nasty bug which causes incoming data to be corrupted under heavy network loading, which will happen if you set the number of connections too high. That said, this usually doesn't lead to crashes, but visually corrupt images being rendering on webpages.

I should also add that stack size is not the issue here.

[futaura]

VooDoo wrote:
I run IB whit 8 connections..now I will test whit 6 and whit running StackAttack..I will post results..

8 should work fine - I use 10 on a 2Mbps connection, but then I have an 060, so maybe your slower cpu is a factor. It's just that some people think that since they have ADSL, it would be a good thing to bump up the connections to 32 :-)  The truth is that this is only the case if your cpu is fast and is not being used to the max.  Browsers on classic Amigas simply can't cope with that amount of incoming data - decoding 32 images simultaneously isn't going to be any faster than decoding 8 images simultaneously, then another 8, another 8 and another 8.  Basically, the faster the data arrives, the faster your cpu needs to be for a browser to fully utilize the network speed.

I still think it's more likely just to be sites triggering IB bugs though.

[futaura]

itix wrote:

Don't use the "Back" button.

Pressing "b" instead of "Back" button cures 'back button crash'.

Which crash is this?  Is it easily reproducable?  I don't recall fixing such a bug, or even hearing of it.  Certainly, pressing "b" should make no difference compared to pressing the button itself, since the exact same code is triggered.