Stack Overflow at line: 0

**BAndrew** · 09-08-2014, 02:53 PM

I randomly get a "Stack Overflow at line: 0" error without any reason. I don't know why. Does anyone know why this happens? More importantly does anyone have a solution? I already searched google, but I can't fix it.

**Mudbill** · 09-08-2014, 03:57 PM

Your stack is probably overflowing.
http://www.stackoverflow.com

So you're talking about Amnesia doing this or what? I've actually never heard of that before.

**BAndrew** · 09-08-2014, 05:42 PM

No, amnesia doesn't cause this (it's off topic after all). I don't know what is causing this. How do I fix it?

**Froge** · 09-08-2014, 05:47 PM

do you have an infinite recursion

**MrBehemoth** · 09-08-2014, 05:52 PM

A quick google implies it's a JavaScript error. What are you doing when it happens? You need to figure out what program or website is actually having the error.

You like mysteries right? Get deducting!

**BAndrew** · 09-08-2014, 05:56 PM

Usually it happens when I am surfing the Internet (with Chrome), but it also happens when I don't.

That's not a mystery! It's boring and annoying!

**Mudbill** · 09-08-2014, 08:00 PM

It can happen in Java as well. It might happen in C styles too, but I don't know for sure. But if it happens when you browse the web, it's either JavaScript or Java. Depends what you're doing, really. JavaScript is used all over the web, and Java is used for applets and applications. So if it happens outside your browser, it's more likely Java, cause JavaScript is pretty much browser only.

Since you didn't specify I just assumed you were talking about Amnesia. People tend to get lost on these forums sometimes.

**BAndrew** · 09-08-2014, 08:30 PM

OK sorry for not specifying.
I believe it's javascript because when I go to the javascript console on my browser it displays a few errors.

**Mudbill** · 09-09-2014, 07:19 AM

It's still hard to diagnose if you don't even know what you're trying to do when it happens. If it's just a specific JavaScript that messes up, then it's probably the author's fault. If it's all JavaScript then that's a bit more of a problem.

**BAndrew** · 09-09-2014, 09:43 AM

(09-09-2014, 07:19 AM)Mudbill Wrote: It's still hard to diagnose if you don't even know what you're trying to do when it happens. If it's just a specific JavaScript that messes up, then it's probably the author's fault. If it's all JavaScript then that's a bit more of a problem.

It hasn't occurred since yesterday. So maybe a specific website has a javascript error in its code and when I visit it, it displays an error.