IE7 crashes when trying to use history. Where do I turn?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I see there is no forum for IE7 issues. That seems a bit strange to me as
there seems to be alot of talk about IE7 problems. I have one myself that I
have not seen documented yet. Maybe someone else has.
I was running IE6 on my old computer and had no problems at all. Same
goes for my new computer. In each case, when I updated to IE7, it crashes
every time I use the link pull-down to go to a site in my history. Even if I
just open the pull-down and do not select a different site, it still crashes.
The error simply says "the application has encountered an error and must
shutdown".
I tried uninstalling IE7, which left me with the fully functioning IE6
code. That works fine. No crashes. Of course as soon as my system does it's
automated update, IE7 is back, along with the same crashing problem.
Other than this issue, I like IE7. I like the tabs and such. It's just
a shame that this issue is ruining IE7 for me. Anyone have any idea how to
fix this issue? Right now, I would even be happy to hear that it is a known
bug and will be patched shortly. I am just starting to feel like I am the
only person with this wierd issue.
Thanks in advance if you have any thoughts on this matter.

KevKaos
 
In KevKaos had this to say:

My reply is at the bottom of your sent message:
I see there is no forum for IE7 issues. That seems a bit strange to me
as
there seems to be alot of talk about IE7 problems. I have one myself that
I
have not seen documented yet. Maybe someone else has.
I was running IE6 on my old computer and had no problems at all. Same
goes for my new computer. In each case, when I updated to IE7, it crashes
every time I use the link pull-down to go to a site in my history. Even
if I
just open the pull-down and do not select a different site, it still
crashes.
The error simply says "the application has encountered an error and must
shutdown".
I tried uninstalling IE7, which left me with the fully functioning IE6
code. That works fine. No crashes. Of course as soon as my system does
it's
automated update, IE7 is back, along with the same crashing problem.
Other than this issue, I like IE7. I like the tabs and such. It's
just
a shame that this issue is ruining IE7 for me. Anyone have any idea how to
fix this issue? Right now, I would even be happy to hear that it is a
known
bug and will be patched shortly. I am just starting to feel like I am the
only person with this wierd issue.
Thanks in advance if you have any thoughts on this matter.

KevKaos
Click to expand...

Load IE without add-ons from the right click menu from the icon on the
desktop - problem may go away. If it does then debug it by removing add-ons
one at a time or removing all of them and adding them back one at a time.

In addition:

For IE7questions please see:

In a newsreader:
news://msnews.microsoft.com/microsoft.public.internetexplorer.general

On the web:
http://www.microsoft.com/communitie...?dg=microsoft.public.internetexplorer.general

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/ http://kgiii.info/

"Chance has put in our way a most singular and whimsical problem, and its
solution is its own
reward." - Sherlock Holmes
 
Galen, Thanks for the info. You were spot on correct. I had a little trouble
at first figuring out how to block the add-ons. It seemed a bit different
than how you described, but that my have just been my misunderstanding.
Anyway, I starteddisabling them one at a time and restarting IE 7 and testing
after each one. I got to the end of my list, and there were three items from
the same software package and I could not disable them without uninstalling
the software. I did uninstall it and the problem was resolved. The software
is StopZilla (which I love). They have a 24 hour support chat line, so I
contacted them about a possible bug. Turns out that they know all about it
and said that an update will be coming out very soon. They sent me an advance
copy of the new release and it is working great. Thanks again for your help
even though I didn't post in the correct area. I love IE7 now.

Kev
 
In KevKaos had this to say:

My reply is at the bottom of your sent message:
Galen, Thanks for the info. You were spot on correct. I had a little
trouble
at first figuring out how to block the add-ons. It seemed a bit different
than how you described, but that my have just been my misunderstanding.
Anyway, I starteddisabling them one at a time and restarting IE 7 and
testing
after each one. I got to the end of my list, and there were three items
from
the same software package and I could not disable them without
uninstalling
the software. I did uninstall it and the problem was resolved. The
software
is StopZilla (which I love). They have a 24 hour support chat line, so I
contacted them about a possible bug. Turns out that they know all about it
and said that an update will be coming out very soon. They sent me an
advance
copy of the new release and it is working great. Thanks again for your
help
even though I didn't post in the correct area. I love IE7 now.

Kev
Click to expand...

Excellent, I'm really glad to hear that. There will be a lot of authors who
will be needing to update their add-ons/plug-ins for quite a while to come.
I'd like to take a moment to thank you for coming with the right sort of
attitude. A lot of people come in spouting about how this is Microsoft's
problem and how Microsoft needs to fix it. I don't want to stand on the soap
box right at the moment (I'm still playing catch-up for having taken the
weekend off for the most part) but the reality is that it is the ISV
(independent software vendor) who has to code for the browser, OS, etc... It
isn't the OS or framework maker who codes for the plug-in. A lot of people
come insisting that it is the other way around and that Microsoft has to fix
everything.

As a side note - and partially a step on the proverbial soap box - it is a
good thing when they stop working to maintain backwards compatibility, that
is where a lot of bugs and security exploits come from in software. People
think that it is all a game and that they take that old stuff out just to
force people to upgrade (and to some extent that may well be true) but the
reality is that leaving it in there leads to everything from performance
hits, bugs, and security holes. Upgrading is a fact of life as are updates -
there will always be updates and upgrades. Even if the software model as we
know it dies and it all goes to SaaS and everything is delivered via the
web, there will still be upgrades. (Just not on the end-user's PC nearly as
often.)

Anyhow, sorry for the digression and soap box stomping as well as for the
delay in responding.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/ http://kgiii.info/

"Chance has put in our way a most singular and whimsical problem, and its
solution is its own
reward." - Sherlock Holmes
 
Back
Top