We Keep Coding

Only getting RangeError when Chrome Developer Tools is closed

So I have this weird error where the script stops executing with RangeError: Maximum call stack size exceeded when I launch it normally, but when I open the Developer Tools and launch it, it loads up perfectly well.
It only happens in Chrome/webkit based browser; it works perfectly fine in firefox. I don't have any code to post here because it points to compiled wasm code (that wasn't written by me).
But what I can't understand is that why it works in Firefox, and on Chrome (with dev tools open) but doesn't work normally in chrome.
Thanks.

Javascript "TypeError: Load Failed" error when calling "fetch" on iOS

I'm logging JS client errors using Sentry and there's a lot of "TypeError: Load failed" errors. It's only occurring on iOS. I can't find anything on Google. Is this a native Javascript error or something else? What does it mean? This is separate from a seemingly related issue with "TypeError: cancelled".
Screenshot from Sentry of the breadcrumbs

From what I understand, the fetch API may deliberately return very limited error details on failure. (Otherwise, a malicious JS program could issue a variety of fetch requests and look at their results to identify which internal servers exist, which servers the user has access to, etc.)
If you have access to a Mac, you can see this for yourself by experimenting with fetch requests from the Safari DevTools console. For example:
The request for google.com fails due to CORS. The request for example.does-not-exist is an invalid name. The DevTools console gives full details, so a developer who's actually at the browser can troubleshoot, but those details aren't available to JS code; the JS code gets the same "TypeError: Load failed" message in each case.
If you're lucky enough to have a way to access the browser console, you can see more details, but otherwise, I'm not aware of anything you can do to track down the problem - it could presumably be virtually any network error.

Had the same problem, problems occured because of certificate and iphone took addres api as dangerous.
Helped me get into address api directly in safari or chrome for instance: https://my-adres-api/api/product and then choosing allow to connect with that address.
Now requests works excellent

In my case, this issue appeared mostly on iOS 15 in Safari. By debugging an iPhone through Mac I found that preload links with imagesrcset are not handled well in Safari (unless de-prioritized), throwing <link rel=preload> has an invalid imagesrcset value, as described in this question.
The reason why it looks like fetch error in Sentry is that preload link actually uses fetch under the hood.
Given it's just the image preload that is failing, and unless it's causing you performance problems, you can safely ignore this particular issue in Sentry until this webkit Bug 231150 - Safari complains about invalid imagesrcset value in where Chrome doesn't gets fixed.

Safari inspector doesn't show javascript errors

For some reason, since High Sierra and now Mojave, Safari no longer shows page breaking errors in the Inspector console. If I load a page that has a fatal error there is nothing output to the console. Other errors, such as cross origin blocking, 'XMLHttpRequest cannot load' or 'Failed to load resource:' errors DO show up however anything like a reference error or plain broken code show nothing. If the same page is loaded in Chrome or even in Safari Technology Preview it works as expected—displaying the appropriate error in the console. Is there a preference somewhere I've inadvertently switched? It's driving me nuts.

Firefox mobile error console missing

I'm working on a mobile website, and it works fine in the Android stock browser. In Firefox some JavaScript functions don't work. So I was googling for the error console. I found a support page wich gives information about the error console of an early version.
Is there an error console in Firefox for mobile version 14 (2012-06-26)?

Looks like it is hidden, but adding browser.console.showInPanel and devtools.errorconsole.enabled then setting both to 'true' in about:config will enable the console and preferences panel for JavaScript debugging purposes.
Here is how to find the error console icon:
Firefox Mobile: Enabling the Error Console
It seems that the Error Console is deprecated, so bookmarklets are the simplest of the remaining mobile debugging alternatives:
Android Console:
javascript:(function(){if((/android/gi).test(navigator.appVersion)){console={"_log":[],"log":function(){var%20arr=[];for(var%20i=0;i%20\""+value+"\"");}},"show":function(){alert(this._log.join("\n"));this._log=[];}};window.onerror=function(msg,url,line){console.log("ERROR:%20\""+msg+"\"%20at%20\""+"\",%20line%20"+line);}window.addEventListener("touchstart",function(e){if(e.touches.length===3){console.show();}});}})();
Firebug Lite:
javascript:(function(F,i,r,e,b,u,g,L,I,T,E){if(F.getElementById(b))return;E=F[i+'NS']&&F.documentElement.namespaceURI;E=E?F[i+'NS'](E,'script'):F[i]('script');E[r]('id',b);E[r]('src',I+g+T);E[r](b,u);(F[e]('head')[0]||F[e]('body')[0]).appendChild(E);E=new%20Image;E[r]('src',I+L);})(document,'createElement','setAttribute','getElementsByTagName','FirebugLite','4','firebug-lite.js','releases/lite/latest/skin/xp/sprite.png','https://getfirebug.com/','#startOpened');

Safari for Ipad not reporting line numbers on Javascript errors

I am using iPad 2 with IOs 5 to develop a web application.
I have enabled the developer console to get logs , but when javascript error occurs it does not include corresponding line number.
Since the web application handles touch and gesture events, I cannot test them on desktop version of the browser!
Any help will be appreciated.

You can add a window level error handler
http://dev.opera.com/articles/view/better-error-handling-with-window-onerror/
and have that console log the line number. You'll be getting two console logs per error, but you will have more control over the output.

You can try using regular Safari or Chrome and write it there first before using the iPad or alternatively there is the Weinre application that provides you a console like firebug / chrome developer tools.