Spent 3 hours debugging and it was a missing semicolon

I was sitting in my dorm room at midnight trying to figure out why my JavaScript loop was crashing the browser. Turned out I forgot a single semicolon after a variable declaration. My friend walked over, looked at it for 10 seconds, and pointed it out. Has anyone else had a tiny typo waste hours of their time?

2 comments

2 Comments

the_jason9d agoTop Commenter

Missing semicolons usually don't crash a whole browser though. Might be something else going on in the code that was the real problem, the semicolon just happened to be the first thing you noticed.

alicew689d ago

Totally agree @the_jason, I once spent an hour tracking a "typo" that was actually a broken callback.