Bug Tracker

Opened 11 years ago

Closed 11 years ago

Last modified 8 years ago

#3376 closed bug (worksforme)

IE6 browser crash on page

Reported by: Binary Owned by:
Priority: minor Milestone: 1.3
Component: core Version: 1.2.6
Keywords: ie6, crash Cc: Binary, flesler
Blocked by: Blocking:

Description

I have a web page that does not contain any jQuery code, but jQuery is loaded in the header.

In IE6, the page crashes the browser. Sometimes it's not the first request, but a refresh will crash it.

So far I've found two things:

  • If I take the jQuery script reference out of the header, the page does not crash.
  • If I leave jQuery in place, but remove the large table from the HTML, then the page does not crash.

No other browsers are affected.

I thought it might be something to do with the length of ID's on the elements in the table (they are generated by ASP.NET) but if I string replace them in the HTML file with shorter equivalents a crash still occurs.

I'm sure it's an IE issue but thought I'd log it in case anyones got any ideas, we're having to resort to not loading jQuery for IE6 browsers on specific pages on our site.

Attachments (1)

crash ie6.htm (65.7 KB) - added by Binary 11 years ago.
Page that crashes IE6 when jQuery loaded in header

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by Binary

Attachment: crash ie6.htm added

Page that crashes IE6 when jQuery loaded in header

comment:1 Changed 11 years ago by Binary

Just to update this, it looks like a bug in certain versions of mshtml.dll. It doesn't happen on all machines that are running IE6, some versions are ok. There are a number of fixes for IE6 crashes that Microsoft offer, so this looks like the problem.

comment:2 Changed 11 years ago by flesler

Cc: Binary flesler added

comment:3 Changed 11 years ago by brandon

Resolution: worksforme
Status: newclosed

Seems to be working for me but as you said it probably relates to certain versions os mshtml.dll. My only suggestion is to cut down on the amount of html you are outputting. That is a lot of information for IE to keep in its fragile memory. :(

Note: See TracTickets for help on using tickets.