Browser Crashing

[Hunee]

In the last week or so My browser has begun crashing on EQtraders when searching the database. Sometimes I can click around a few times, often it is just a couple links then it crashes. Seems to happen most off the Quick Trivial lists.

Has anyone else noticed this or have an idea how I can fix it?
Havent noticed it happening on any other websites.

[adrift]

Happens to me also. I noticed this problem after I downloaded newest Yahoo toolbar and also latest patch for win 2000. I also hope someone can identify problem.

[Verdandi]

What browsers are you using? IE?

[adrift]

Brower is IE.

[Hunee]

Yes, IE here too

[Verdandi]

Kyros or Ngreth, any idea? I only use Firefox and haven't had any problems.

[Ngreth Thergn]

no idea because nothing has changed and it is just a text file, about 2 images, no java or such... Only thing I can think of is some posible odd ads maybe

It can be a LARGE text file...

[Brodder FoamyMugs]

chache 265 character file reference overload protective references in IE are being tagged on large file searches in the DB Ngreth. Comes from what I assume are the older databases and the newer format hooks (that's links to a database keyword search file) being vague or specific enough to trigger the new security issue.

Instead of addressing the large search overload security risk the memory file overload triggers a IE crash instead.

This same thing happens when you have more than one video or song playing on multiple players on the computer (ie using quicktime, flash 8+ and Microsoft's own Player (V10 and V11Beta).

It's a pure IE security problem from what I've been able to replicate from what folks have said here so far and reading the memory locations that cause the security trigger to go off.

It may be something old also residing in a page (bad link with bad code hidden in the preload) too.

A few passes of the code in the database to make sure it all conforms to the character limitations and formats you're currently using should reduce the problem, but that's a weekend's worth of work Ngreth and I'm reading the what and how fors directly out of the old IBM machine language registry manipulation book that disected old MS DOS and inherent problems.

Funny 90% of those problems still exists in all new forms of MS, but are later patched. Gives the Virus and firewall companies plenty to look for and sell protection against.

I've long wondered if MS didn't create the Firewall and virus community on its own via cut outs...but that's tin foil hat talk I'm sure.

Large searches done in quick succession fill the history buffer and search buffers and can cause the specific registry that checks overflow code for security violations.

They white washed the fix and patched the holes with a new entire wall vs fixing the code problems.

Get one of the EQ geeks to check the sec registers- they'll know which of the 8 registers to look at and watch code interupts and lock ups for.


Lucky I just happened to be cleaning up my old college books. It's a wonder they don't teach new programmers what occurs at the registry level and machine code these days...and it's a wonder I remembered the MS alert about that fix a few months ago...

I'd blame the drugs the VA gives me, but they suually make me a zombie instead.

Hope I'm on the right track at least.

Dick

[Carmaris]

My wife was having the same problem surfing her digital scrapbooking pages. I reinstalled IE6 from the microsoft website and she hasn't had a problem since.

[YurienStonebow]

same problem. i copied the error message if anyone can help..... it said that 0x77fcaff8 cannot be referenced at 0x22d7369, cannot be written

[Brodder FoamyMugs]

That's the overflow protection buffer register. Do a windows update and see if that helps. If not goto MS and FORCE download IE and reinstall it (not repair- reinstall) then do all the patching again.

You don't need to fully reinstall windows to fix this error.
MAKE sure you make a roll back marker before you do this!!!

[adrift]

Switched to Firefox

I was intending to switch to Firefox, this finally motivated me to punt IE. I can verify that Firefox does not have this problem.

[Hunee]

Windows update had a patch for IE this morning, Haven't crashed yet since updating.