|
So we're experiencing an issue on IE with our website.
Open up the console and... IE crashes 
This isn't even an issue on other browsers and it just crashes IE completely!
I've seen this behavior before and, like now, it's a syntax error in JavaScript.
Last time I was able to debug it with VS2015 attached, this time even that won't help.
So far I've found out that the issue is in jQuery, but before I can do anything else IE crashes and I've lost my debug session.
The weirdest part is it only crashes when I open up the console.
If I just open the website there is no problem.
Well done IE, not only are you a horrible browser, you've also made it difficult, if not impossible, to debug the issues that we'll certainly run into when using you.
Will IE just die already? 
|
|
|
|
|
Sander Rossel wrote: Will IE just die already?
I don't think is dead...
Drunk? Retarded? Messed up?... that's another question
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: Drunk? Retarded? Messed up?
I have some JavaScript to go with that! 
|
|
|
|
|
Sander Rossel wrote: it only crashes when I open up the console.
I'm more worried about the code you wrote. It must be really bad to crash the console. 
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'm not sure what the problem is.
Recently, this awesome new ES2015 syntax did the trick:
var s = '';
var o = {
s
};However, I can't seem to get it to work locally.
Could it be that there's a difference in how IE handles JavaScript coming from the server and local JavaScript?
|
|
|
|
|
|
I don't know where the semicolon would be inserted in that snippet.
Anyway, even if that was the issue, why would IE crash completely?
I had expected the page not to load (fully) and a console log error stating there's a syntax error in my JavaScript.
I do not expect the entire browser to go down.
|
|
|
|
|
Automatic semicolon insertion is quite known to be both not implemented according to standards and differently between browsers. But I'm just guessing here, partly from experience though.
Sander Rossel wrote: why would IE crash completely
Is that a trick question?
|
|
|
|
|
IE?
IE?!?
You're still using IE?!?!?
You should be using Edge! It's Universal!
As in, it doesn't work universally, not just in a few special cases.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm using neither, our customers do
Personally, I always take a shower after having used IE.
|
|
|
|
|
Emm - I - Cee - Kay - Eee - Why(?) - Ess - Oh - Eff - Tee [^]
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
One Browser to rule them all, One Browser to find them, One Browser to bring them all, and in the darkness bind them
|
|
|
|
|
So much for getting away from that Mordor theme. 
Still, if I want to write some kind of web application, I'm going to forget that crappy browsers and JawaScript even exist. Even if that means that I have to write my own UI.
Wait a second...
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
You could go for another theme.
JavaScript, this isn't the language we're looking for.
It takes a great deal of courage to stand up to your enemies, but even more to stand up to your JavaScript.
The first rule of coding: you do not talk about JavaScript.
I love the smell of JavaScript in the morning!
I'll make my own front-end script with blackjack and hookers!
|
|
|
|
|
Sander Rossel wrote: JavaScript, this isn't the language we're looking for.
Close. I suspect it's really JawaScript[^]. If the droid on the picture is one of those we are looking for...
Anyway, what do you expect from a language from little scavengers on some desert planet?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: Anyway, what do you expect from a language from little scavengers on some desert planet?
Still something better than JavaScript
|
|
|
|
|
|
Sure, IE sucks.
Sander Rossel wrote: So far I've found out that the issue is in jQuery,
Why Sander, WHY!!!!
That's for the children.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
|
Debug ie in FireFox?
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
You are not debugging IE. You are debugging the javascript that kills IE.
Firefox can handle errors and bad JavaScript better than IE. Sometimes debugging the problem Javascript in Firefox will show you what is crashing IE.
|
|
|
|
|
Not possible, unless I'm using an older version of Firefox, but I don't know which one.
It's some CSS compatibility issue.
I know exactly where the code goes awry, I just don't know why it crashed my dev tools and entire browser.
When run without dev tools it behaves as expected.
|
|
|
|
|
Yeah, you'd think... Except, there is no error.
Apparently, jQuery gives an invalid selector to Document.querySelectorAll()[^] which makes it throw an error.
The call is in a try-catch block so you'll never even know an error occurred.
I've debugged this in Visual Studio and in other browsers and the behavior is exactly what you'd expect.
Even IE has no problems with it.
Except when you open the dev tools.
That somehow makes the browser crash 
I'm thinking there's no bug in the code, but in the dev tools.
|
|
|
|
|
Sander Rossel wrote: Except when you open the dev tools.
Ah, I see now. Not so much with the browser but with the dev tools.
|
|
|
|
|
Whatever it is, it's impossible to debug this page on IE 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
