Member Avatar for jimmyye0h

Hi,

Our site (www.iloho.com) works fine on FF, Chrome and Safari but on IE it seems to freeze on the home page after signing in.

We've been trying to resolve this for a week and sadly there's no meaningful progress.

Is anyone able to point out which areas we should look into?

Cheers
Jimmy

  • 4 Contributors
  • 4 Replies
  • 229 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Member #120589

Dani AI

Generated

This looks like an IE-specific runtime problem that only appears after the login path executes. Common root causes are JavaScript errors that other browsers tolerate, synchronous/blocking XHR or long-running loops, and a different document-mode/compatibility path in IE that executes alternate code. The quickest wins are (a) capture the failing error even when the devtools can’t be opened, and (b) reduce the login flow to a minimal repro so you can binary-search the faulty module.

Quick checklist and small fixes to try first:

  • Run IE with extensions disabled (iexplore.exe -extoff) and test in a fresh profile to rule out add-ons or toolbars.
  • Add a tiny console fallback so stray console.log calls won’t throw in older IE builds:
if (!window.console) { window.console = { log: function(){} }; }
  • Install a global error catcher that persists the error for later inspection:
window.onerror = function(msg, url, line) {
  try { localStorage.setItem('ie_last_error', JSON.stringify({msg, url, line})); } catch(e){}
  return false;
};
  • Grep the code for: trailing commas in object/array literals, synchronous XHR calls (open(..., false)), heavy DOM loops, or code using modern JS features unsupported by targeted IE versions. Also check for a forced Compatibility View or an absent/incorrect X-UA-Compatible header/meta.

A focused workflow that helps isolate the culprit:

  • Reproduce the freeze with F12 open if possible; enable "break on exceptions" and watch the Network tab for stalled requests.
  • If the page dies before devtools attach, deploy the console shim + window.onerror, then sign in and reload to read localStorage or a small server-side error endpoint.
  • Reduce the login flow: strip UI widgets and third-party scripts, test in small increments (binary search) until the freeze disappears.

This expands on ’s console tip and ’s breakpoint idea. Since asked for code, a minimal HTML+JS reproduction of the login callback (IE version noted) will be the most actionable next artifact for diagnosis.

Recommended Answers

All 4 Replies

Member Avatar for lambing

have you seen the console log of IE's web development tool?

Member Avatar for jimmyye0h

since IE crashed before the loading was done, the console log was not accessible. We just had to force quit.

Member Avatar for gon1387

Have you tried "debugger;" to put breakpoints in your code?

MyLogin = function(){
    this.loginUser = function(){
        //getData through AJAX

        // insert the debugger to create a breakpoint; script stops here
        debugger;
        this.prepareUserData(userData)
    }
    this.prepareUserData = function(userData){
        //... implementation for preparing user data
    }

}
Member Avatar for Member #120589

ANy chance of showing your code? Couldn't test it without signing up.

Edited by Member #120589
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.