We Keep Coding

What does the "glGenSyncTokenCHROMIUM" error mean?

I'm debugging a WebGL application, and the following error message pops up in my console, right after a call to compileShader() and getShaderInfoLog():
GL_INVALID_OPERATION : glGenSyncTokenCHROMIUM: fence sync must be flushed before generating sync token
I've searched teh interwebs for glGenSyncTokenCHROMIUM, with no avail.
(This error seems to be hardware-specific, as I can only reproduce it on a GT-I9505 when running Chrome)
What does this error mean, and/or how can I get more detailed information of what's going on?

It seems to be indeed device/GPU/driver problem. There's bug in Chromium bug tracker (by the way, you can provide your case to it).
There're several ways to get information and help on WebGL bugs. Besides StackOverflow, there is WebGL google group (browser developers also active in it). Bugtrackers may be helpful (you always can and should report bugs to developers). And, if you feel like it, Chrome and Firefox have excellent code search engines (ff, cr), more than once I've found answers to my questions there.

jQuery v2 showing as potentially suspicious

We have had an alert in Google webmaster tools saying there was a malware issue on our site, however it didn't provide any example urls and has since been reviewed and cleared. Trying to do some digging as to why this occurred using an online scanner (http://scanner.pcrisk.com/) it has flagged jquery-2.1.4.min.js as being potentially suspicious.
The details I got from the scanner were as follows:
/styleassets/javascript/jquery-2.1.4.min.js
Reason:
Detected potentially suspicious content.
Details:
Detected potentially suspicious initialization of function pointer to JavaScript
method eval <code> = eval; <code/>
I can't be sure if this was causing the issue but want to try and find out more. I've had a search and haven't found anything directly related to why it would be flagged.
Does any know if this is an issue or has anyone found similar with a version of jQuery?

Speed up debugging in Javascript that use remote API

Lately I have been learning some Google Map API. I have this line of code:
var paths = this.getPath;
The correct line of code should be:
var paths = this.getPath();
I spent way too much time to figure it out. Pressing Ctrl-Shift-J, try catch in Javascript did not give me a clue.
Is there any tool that tells me that I am wrong when I'm working with a remote API so that I do not make the same kind of mistake in the future? My previous experience working with Java using IDE is much smoother thanks to the syntax error highlighting feature.
Edit: In short, how can I detect a mistake when writing the code, not in run time?
Thank you and best regards

If you're using Chrome (I assume you are from your reference to Ctrl-Shift-J), you have an excellent Javascript debugger that allows you to add breakpoints, inspect variables, view the stack, step up and down the chain, etc.
When you realise you're not receiving the results you expected, the best policy is to set breakpoints on and after the calls to the Map API, and inspect the value of your variables before and after. This would reveal that getPath was a reference to a function and not a returned value.
As a general tip, properties prepended get tend to be functions. If it were a property, it would likely be path as opposed to getPath. The verb gives it away.

Use WebStorm as an IDE. It provides excellent features as code completion, debugging, jslint/jshint,... The best IDE for javascript imho.
Combined with Chrome for testing it rocks!

I think those kind of cases may be covered by your debugger as long as you've toggled the pause button at the bottom left corner to "Pause on all exceptions" (the light blue mode).

IE 10 developer tool's (Strangely the counterpart of Chrome, Firefox failed to notify me my errors, I am retesting this part) debugging can help me out. I will inform you more.

Getting very strange javascript error and this page also refuses to work in Internet Explorer 7 or 8

This is the page I'm working on... http://schnell.dreamhosters.com/folio/earthquake.html
Its purpose is explained via the instructions on the left. I'm finding that after doing so many searches and clicking so many of the links in the list on the right that the page freezes up, the Google Map stops working and Firebug tells me of an error in main.js and it goes like this...
b is undefined
Line 49
I really don't know why this decided to happen all of a sudden and the error is so cryptic and muddled amongst Google's code that I don't think I'll be able to figure this one out by myself.
Another problem I'm finding is that the page itself simply refuses to work in IE7 and IE8 (or probably any version of IE for that matter). I am also at a loss as to how to solve this problem because I can't figure out how to use any of IE's debuggers (if they even have one) and seeing how I already tested this and made it work in two browsers (technically three since Safari runs off WebKit just like Chrome), I just don't have the drive or capacity to imagine what could be going wrong.
Any help would be greatly appreciated

Moved from comment to answer.
As scunliffe mentioned, you are trying to do a crossbrowser AJAX without using jsonp. Use either $.ajax() with datatype jsonp or add a &callback=? at the end of the URL in the $.getJSON() call.

IE8 is quite good when it comes to helping out the developer. From memory F12 will open up the developer window where you can inspect the DOM, CSS and debug script.
Your error is cryptic because most javascript comes minified, so variables are all remapped to single letters, etc. See if the script causing the problem has a development (i.e. unminified) version as this will make a lot more sense to step through.
With regards to your specific issue it sounds like a timing issue. While browsers do a decent job of executing script in a consistent way if you follow standards, they do differ in their timings i.e. when things execute. That would explain why b is undefined in some cases and not others.

Permission denied to call method Location.toString

I'm using YUI,
and sometimes I'll see this "Permission denied to call method Location.toString" error,
It's reported in connection.js,
I didn't find any clue why this error occur yet.
Very strange

If you are dealing with any Flash through a cross-domain iframe, then it is quite possible that you are seeing a bug in Adobe's Flash Player that occurs with FF2 and FF3.
The bug is in Adobe's public JIRA here: http://bugs.adobe.com/jira/browse/FP-561
There seems to be no motivation to get it fixed, unfortunately.

If the script is executed from a different domain, or you are trying to access the contents of a frame/window/iframe of a different domain, you will see this error. Safari's behavior was a little different, at least in the v1-2 era (iirc), so you will probably want to test in that as well.
If you are including scripts via a different domain, you need to make sure your actual triggers/events are tied in and executed from inline scripts, or from a script file loaded from the same domain as your html for best results.

Hi I've answered a similar question
why/where the error “Permission denied for to call method Location.toString”.
This is caused by firebug showing errors from other windows in your console. In short, these errors will probably be nothing to do with your code at all.
If you want to test this theory, you can close all other windows in firebug, clear your console and test just your site.

Are you seeing this in Firebug, by any chance?
I'm getting the same thing in Firefox, off-and-on, after adding jQuery to my site. I'm calling the jQuery js from another site (different domain completely), which I figure isn't much different than calling it from Google's servers.
I have no code using jQuery at all as of the moment. And, while Firebug reports this as an error, it doesn't do so all the time. While I have it turned on, I'm seeing no errors in IE.
While there are different libraries involved, my guess is that Firebug is generating a false-positive.
Now if you're not using Firebug when you see this ... are you using YUI hosted on your own server? What browser are you using? Etcetera.
~James