Why would this web page cause IE6 to lock up? [closed] - internet-explorer-6

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
I'm stumped. From what we can tell there is nothing wrong with this page and it renders fine everywhere else (IE7/IE8, FireFox, Opera, Safari, etc). The problem is that if it's loaded in IE6 on Windows XP SP3 it just locks up the browser and it has to be force-closed through task manager in most cases. A few of our test computers load it fine, but others just up and die like they joined a cult and drank the punch. We're at our wits end trying to identify the problem, or even what is special about the computers where it works or doesn't work. Any thoughts?
http://www.centerforsight.net/doctors-staff/providerDisplay.cfm?staID=8
Responses like "why are you using ColdFusion" or "because IE6 sucks" won't help me. Our client is stuck with IE6 for the foreseeable future and needs their web site to work in that version. Any insight into the actual problem are greatly appreciated, however. Thanks in advance!

It sounds like that something in the JS files gets locked into an infinite loop on IE. Why don't you try putting in alerts into the JS functions that get called to try and isolate the piece of code that locks the browser.
IE's JS engine is full of bugs and you probably found one.

Try loading it inside IE Tester and see if it offers any clues.

Save a copy of the page on your local machine with Firefox. Loadup the page IE 6, does it hang? If no, find out what firefox is not loading, if yes starting removing stuff from the page. Start removing script tags one by one until you stop it from crashing, when you've tracked down a specific problem, try reposting the question to get a better answer about how to fix the JS issue :)

Maybe it has something to do with Javascript code. IE6's engine is undoubtedly much less well designed than that of other browsers.

It's either javascript or it's waiting to have information dumped from a buffer. If the entire page loads in one giant blob and gets sent (and has a lot to it) it can also overwhelm IE and lock it up. (or at least lock it till the glob gets rendered)

Do they have the latest version of IE6? Have they run Windows Update recently? Maybe there's some obscure bug that is fixed in a patch or service pack.

Related

"retry page load" in content.js file *** website root ***

I get this message every time my page loads for the first time. It really bugs me and my experience while I try to use console for testing my app. I tried looking for the solutions on google but didn't get them. I don't know if this is some basic issue so in case it is, I would really appreciate any help I get.
I expect to remove this message from my console using some setting or maybe by entirely fixing it.
Check your browsers extensions, it is usually caused by the ad-blocker or similar.

After updating Notes client / designer help navigator is broken

Last week I tried to update my Notes client installation from 9.0.1 FP9 to FP10 IF 3. For technical reasons I had to roll back which proved to be quite difficult, and I ended up completely uninstalling Notes and doing a fresh installation of 9.0.1 (standard) then FP9 IF 2.
Everything's fine (and much more responsive than before, too) with one serious exception:
Within the client help popup window for Notes client and Domino Designer help is hardly usable now; obviously there's no CSS style or whatever applied to the nav page / frame:
As you can see in the screenshot styling of the main window part (green frame) is fine. But everything that is releated to navigation (red frames) appears to be raw html. Javascript calls are apparently working but it's really hard to navigate the "chapters". Same applies to Designer help, of course.
Here's what I tried to solve that riddle:
uninstalled and re-installed full client 3 times; sometimes I ran the
installation as local Admin other times I didn't (no difference)
just installed plain Notes 9.0.1 from scratch then tested Client help before updating to FP9IF2 (no difference)
restored the entire [Notes-Programm]\framework directory from a
backup I took when Notes help still was working as expected (no difference)
copied over the entire \Notes\ folder from a different PC where popup help is still working fine (no difference)
Problem with that is: being a Developer I need to have a functioning help window in my Domino Designer. The navigator as it is right now however is plain useless. And designer_help.nsf isn't of help at all when it comes to Java, LotusScript etc. objects and classes.
One of my co-workers has the same phenomenon while another one hasn't.
Question: did anyone else experience something like that? Where you able to solve it? How?
This seems to be related to an issue with the embedded browser windows that Domino Designer uses to open the Help website.
Try to open following link in a modern browser (such as Chrome or Firefox) and the navigation should be fine.
http://localhost:50970/help/index.jsp?topic=%2Fcom.ibm.notes.help.doc%2Ffram_getting_started_c.html
Bookmark it and use it when you need it.
Try using the IBM Nice tool to see if it can fix your issue
https://www-01.ibm.com/support/docview.wss?uid=swg21459714
Meanwhile I restored my entire Windows system partition from a backup created just before all that began (lucky me that I have both regular local backups plus a separate system partition). And that finally helped resolve the problem.
Meanwhile I'm 99% sure that this is due to a rather new registry and/or firewall setting not yet known to IBM's NICE tool.

Domain redirecting without my permission

http://catbreedsinformation.com
A friend and I put that site together a few years ago, just to do some study on how to use google ranking. It was actually doing quite well. Recently, we haven't really messed with it, but I still check the analytics, and they have severely dropped.
I went to visit the site tonight, and it loads for a split second, and then redirects me to a completely different site.
Can anyone explain what is causing this? And also, explain how I can stop this?
thanks.
Looks like your website hacked.
First of all, please change all passwords. Then remove twitter fan box plugin (because script of this plugin is causing redirect)
Then you can check this resource: https://codex.wordpress.org/FAQ_My_site_was_hacked

Google Chrome DevTools elements search not working

Since about a week ago, I haven't been able to search for elements or the contents of an element in Google Chrome DevTools. Did the latest Chrome update break this functionality or has something else changed that I should be aware of?
I first thought I had accidentally changed some of the DevTools settings, but now the same thing started happening on my other dev machine as well, so I think it must be a bug in the latest update?
Is it just me? :)
EDIT: After a few days of wondering what could be possible causing this.. it just started working again after I restarted my Win 7 machine. The simplest fix the best fix, huh?
On another note, if the error starts happening again, I'll need to dig deeper as what might cause it and file a bug if necessary.
For now, it works and I'm happy :)
No results in DevTools element search. Here is a screenshot:
I solved that by disabling "Adblock Plus", it worked in 3 browsers I tried.
This is a legit bug. Thanks for reporting it. It's being tracked here: https://code.google.com/p/chromium/issues/detail?id=426815
As of November, it's been fixed in tip of tree (Canary) and has been merged to the beta branch (39).
(Originally answered by vsevik, an engineer who develops the DevTools, however the post was deleted by moderators.) :/
I had the same issue, search wasn't working, because I couldn't see the page. When I clicked on the page, under the Sources tab, I got a blank page. What worked for me was refreshing the page in Chrome. After that, the code showed up in Developer Tools, and I was able to search the code. This seems to be a Chrome bug.

Handling crash dumps from Firefox and Google Chrome

I'm developing a cross-platform NPAPI+XPCOM extension for Firefox and Google Chrome (Windows, Linux and Mac). I was wondering if anyone could enlighten me on the best practices of handling component crashes.
As I understand it, currently Mozilla's Crash Reporter submits mini-dumps and crash reports created to Mozilla Dev. I experimented with blocking SIGSEV to Firefox and creating my own core in the plugin code. Although that works just fine, I'm sure I'm not supposed to do that.
And Google Chrome doesn't even seem to create any core dumps! Any suggestions?
The firefox crash report database is publicly searchable, so you don't have to do your own handling. If you ask nicely (i.e. prove you're the plugin author) I'm sure they'll even give you the minidumps from your plugin's crashes.
This is awfully late, but yeah, don't do that. You will wind up catching a lot of things that aren't just your plugin, and you will screw up our crash stats. You should be able to find your plugin crashes in our crash report site. If you need better reporting, you can file a bug on us and we should be able to help you.

Resources