Geek Answers Handbook

IE 8 crashes on site load, cannot debug -

http://bizzocall.com/faq/ - works well in all other cases, but when I test it using developer tools compatible with IE 8, it just crashes.

I looked through all the answers and it seems that each person has different problems (I was looking for swearing commas, updated jquery, etc.).

Any help is much appreciated!

UPDATE

I found a plugin that called jquery 1.4 (Dave WordPress Live Search) and uninstalled it. Although the code seems clean, it still pauses IE 8.

UPDATE 2

Removing the plugin seemed to be a trick.

Just for those who find this message: it was a wordpress launch with a theme installed.

+4
source share
7 answers

Crash for me too in IE9 with IE8 mode. (see development tools → F12 ). If you disable javascript, this will not work ... so this is a problem with javascript. I see that you are loading 3 different versions of jQuery, maybe so?

EDIT. I used the debugger and froze during jQuery 1.44 runtime (you load this library in the footer from Google CDN)

+1
source

It seems that most likely you have a trailing comma, not necessarily wandering. For instance:

 { "hello":"world", "foo":"bar" }

It will work fine, but if you did:

 { "hello":"world", "foo":"bar", }

That would completely kill IE. Look at this or maybe give us more hints as to what the error is.

+1
source

When commenting on a script tag fancybox IE does not crash. But I do not know what is the reason.

You call jquery twice: jquery 1.6 and jquery 1.4.4. It seems to have caused a crash. But if you disable jquery 1.4.4, fancybox still fails. Disabling jquery 1.6 to avoid a crash.

+1
source

My IE (IE 8.0 @Windows Server 2003) doesn't get killed when I enter the page.

However, Javascript seems to continue to work forever because IE offers me "Stop the script ... making Internet Explorer run slowly ...". There is also a Javascript error indication there. It says:

 Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET4.0C; .NET4.0E) Timestamp: Fri, 13 May 2011 20:08:46 UTC Message: Permission denied Line: 133 Char: 374 Code: 0 URI: http://bizzocall.com/faq/wp-includes/js/jquery/jquery.js?ver=1.4.4

You said you updated JQuery, but 1.4.4 doesn't seem to be the latest version, did you?

UPDATE:

I ran Developer Tools (F12) to get the call stack, and one of the entries on the stack (only in the middle):

  //jquery.fancybox-1.3.4.js lines 1040-1045 in the $.fancybox.init $('body').append( tmp = $('<div id="fancybox-tmp"></div>'), loading = $('<div id="fancybox-loading"><div></div></div>'), overlay = $('<div id="fancybox-overlay"></div>'), wrap = $('<div id="fancybox-wrap"></div>') );

UPDATE2:

I give up. Javascript / jQuery knowledge is too limited. And the miniature jQuery code doesn't seem to help either. Debugging through things like this.each(function(e){var g=f(this);a[0]=j.call(this,e,c?g.html():b),g.domManip(a,c,d)}) , it seems, is not the easiest thing in the world.

I suggest running the same code with a single jQuery instance (single version, it may be 1.4.4 if this is your choice) in the development version (unminified). Problems may arise if the error does not occur then.

+1
source

Dave from "Dave WordPress Live Search" here. Just wanted to add a few comments:

  • Dave WordPress Live Search does not "call jQuery 1.4." It reports that WordPress is downloading the version of jQuery that it ships with, currently 1.4.4. jQuery 1.6 is not natively supported by WordPress until version 3.2 is released next month. The preferred option for using an alternative version of jQuery is to “unregister” the included jQuery and register your own version in its place. Adding the following to your topic, the functions.php file should take care of this:

     if ( !is_admin() ) { wp_deregister_script('jquery'); //deregister current jquery wp_register_script('jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.js', false, '1.6', false); wp_enqueue_script('jquery'); }

  • Someone recently realized that the jQuery Dimensions plugin included in Dave WordPress Live Search caused IE8 to freeze. This was necessary back when I first wrote this plugin because WordPress comes with an ancient (even for a while) version of jQuery. The functionality provided by this jQuery plugin has been integrated into the jQuery core a long time ago, and since I refused to support WordPress <2.9, it is no longer needed. Give Dave WordPress Live Search v2.1 the back.

+1
source

Try starting IE without add-ons. Often the cause of a full-blown crash is an add-on that interferes with something. For this:

Start> All Programs> Accessories> System Tools> Internet Explorer (without add-ons)

If you cannot find this, go to run promt (Windows Key + R) and type iexplore.exe -extoff

0
source

None of the above solutions worked for me. I eventually tracked it down to an outdated version of Modernizr . Mine was in 2.0.6 and can confirm that version 2.5.3 completely fixed the problem.

0
source

More articles:


All Articles