IBrowse 2.3 crashes on Amiga.org!

[mr_a500]

Have you tried it without the FastExec and Fblit and/or without images? (you say you tried everything, so you probably have, but just asking)

I'm using IBrowse 2.3 on A500 with 68EC020 and have never had a crash on Amiga.org. I get the occasional crash when running out of memory after browsing huge pages with millions of images and javascript, but I it seems that's not your problem. Do you have the latest MUI libs?

What guru do you get?

[mr_a500]

Yes, that's a good idea - delete the cache (and check to make sure everything was deleted). After the first crash, a cached file may have become corrupted and may be causing crashes when IBrowse attempts to load it.

[mr_a500]

Hey, an "Elvis smilie". Thanks. (I think :inquisitive: :afro:)

Argus: I'm glad to hear you solved the problem.

[mr_a500]

Well an update from me: after having hardly any crashes, now IBrowse is crashing almost every single day! I installed no new software and made no configuration changes. Maybe my Amiga is finally dying. :-(

When I view webpages with images now, I can only view a few pages before I run out of memory and I get loads of different crashes. I've had 80000003, 80000004, 80000005, 8000000B gurus and crashes where the screen just flashes random corrupt graphics. After using IBrowse (on the occasions I don't have a crash), huge amounts of memory are not freed, causing me to have to reboot to run anything else. I have no idea why this would start happening when it didn't happen before unless I've got some kind of hardware error. (I did virus checks too)

Damn! My Amiga was running perfectly and now I have to constantly worry about crashes.

[mr_a500]

I delete my cache & history regularly (I follow my own advice, you see ;-) ) so that's not the problem. And I already tinkered around with Chip RAM limits and graphics memory usage. It doesn't seem to make a difference.

I think my problem is memory related. For some reason, memory is not freed and becomes horribly fragmented. After running a large program (IBrowse, YAM), the largest free block goes down to 70-80K (or worse). It never used to be this bad. I've tried programs that claim to prevent fragmentation, but they only slow down my Amiga drastically and occasionally cause crashes themselves.

I think my 68EC020 is fine. I did 3 days constant rendering this week and had no problems. (of course, after I stopped rendering, the next program I opened crashed my Amiga)

To quote a song from "The Naked Gun 2 1/2":
"...well I guess I'm just... screwed."

[mr_a500]

I keep my cache in Ram Disk: as I never need to go back and look through it and what's the point of slowing yourself down and putting wear on your drive?

Well if I put my cache in Ram Disk:, I'd probably be able to view 2 pages before a crash. I've only got 8Mb!  I wish I could put more RAM in my Amiga, but 8Mb is the limit on the Viper.

I'd consider selling my left testicle to get 64Mb in my A500! (not the right one - that one is worth 128Mb ;-) )

[mr_a500]

AAAAAAHHHHHHHHHHH!!! It's getting worse! Now it's about a 100% guarantee that if I have images on, it will crash. I used to browse all the time with images on with no problem.
Recently I've been browsing with images off for speed, but now with images I'm screwed.

Another hint to this bizarre problem: I now usually get software failure popups for IBrowseNetwork. I have IBrowse configured for 4 connections and I just got 4 software failure popups for IBrowseNetwork - 2 were 80000003 and 2 were 80000004. While I was looking at those, I got a final software failure popup for IBrowse. Then my Amiga froze.

Thanks Hyperspeed for the memory test link. I've had a hard time finding one. The only program I have is Bustest and it just checks memory speed (which is fine).

He said "I'm going to cancel your order, Amiga is very old computer 1990 and has maximum memory of 9MB".

Yeah, I laughed when I saw you post that in another thread. At least the guy knew what an Amiga was. When I tried to buy a 2.5"HD for my Amiga, the guy asked me what notebook I had. When I said it wasn't for a notebook, he got all confused and became even more confused when I said it was for an Amiga. When I explained it was an '80's computer, he refused to sell me the harddrive.

[mr_a500]

Javascript is not enabled and MiamiSSL is not checked. I changed nothing in the TCP/IP or IBrowse config (...or datatypes, or installed software or anything).

After my last post, I viewed a few more pages and got another crash - this time with no popups - only graphical corruption then blackout (no guru either).

I ran the Amnesia program and it says my memory is OK. I downloaded IBrowse again to reinstall the image codecs (this time the non-FPU ones), but it still crashed. I have no idea what the problem is. I can usually debug and fix Amiga problems, but with this one I just don't get it. :-(

Hopefully IBrowse 2.4 will come soon and I can start over with that.

[mr_a500]

No, I already removed and put back the Viper and made sure it was well seated.

I don't think SnoopDOS will help in this situation. It's not looking for a missing file. Otherwise no images would be displayed at all instead of displaying until memory ran out then crashing.

I think Enforcer needs an MMU (which I don't have). In fact, I think all similar diagnostic programs require an MMU (I remember searching for these a couple years ago). This is a pity because I think a program like Enforcer would help show if memory is being trashed by a buggy program. I'll check Aminet anyway. :-)