I have a problem with DOM exceptions in Google Chrome as well as in all other Webkit based browsers. I'm working on a Google Maps based data stream browser, and in these browsers it freezes the map after several zoom-ins and zoom-outs.
It throws an INDEX_SIZE_ERR: DOM Exception 1 with a rather unintelligible stack trace. And what's even worse, when I try to use the inspector to pause on exceptions, the tab crashes.
I've tried it in Google Chrome, in Chromium and in Midori, all three give the same result.
I would appreciate any input on how to trace this problem, or on what can possibly be causing it.
Just one last thought - the problem has appeared after Google had rolled out it's API v.3.4. Until recently I have been able to suppress this problem by using the 3.3 version, but now that it has been retired, I have no choice but to face it.
Open up Chrome DevTools (Ctrl-Shift-I on Windows/Linux), switch to the Scripts tab and click the "Pause" button in the status bar (tri-state) until its tooltip shows "Pause on uncaught exceptions", then activate the failing code.
INDEX_SIZE_ERR can happen when accessing a typed array, like an Int8Array or something, outside of its bounds. Are you doing that anywhere?
Related
If you open this site in chrome, it loads and runs ok but I tried loading it in firefox 19.0.2 and I keep getting a Script error asking me if I want to continue or stop. After doing some searching around I found the about:config setting, but that doesn't help. I installed firebug and I see an error about "Permission denied to access property 'toString'" but I have no clue as to what it wants or needs. And the weird part is that if you go to another page in the same site like this one it works just fine. I'm clueless as to what it can be, so any help is much appreciated.
Not a duplicate of this, since it happens on one page but not the other and they both run the same exact code. just that one loads a bit more data than the other. More than anything I'm wondering if its the amount of facebook likes on one page?
When you try to hit play button, you will get a JavaScript error in console in both Chrome and Firefox "TypeError: player is undefined". I tried it and the same error appeared in both console logs. It is and error in the page itself.
I opened it in my firefox browser and it works fine. So it may be there is an add-on which did this error. Try to disable your installed add-ons from (firefox --> add-ons) and reload the page again. If it loads fine then you can enable your add-ons one by one to check which one causes this problem.
I am trying to understand WTF is going with Internet Explore 9, this no mean feat in itself.
I thought the problem was due to browser comparability issues but now I am unsure.
On the staging server I have set the header to Header set X-UA-Compatible: IE=Edge, but it is having no effect.
For example, If I reset the browser, and then open the URL:
http://www.45sound.com/shows/259-heathers-trinity-college-dublin-18-9-2012
Clicking on the timeline, does not move the nob or change the video.
HOWEVER, If I open developer tools, clicking F12, then close it, without reloading the page, it works perfectly...
Is this a loading issue, does anyone know what is going on? I am unsure why this action has an effect on the javascript.
Any help at all would be really great.
Sounds like your code has problems with the weird implementation of the console object in IE - it does create the object only if the devtools are open. See also
Does IE9 support console.log, and is it a real function?
What happened to console.log in IE8?
'console' is undefined error for Internet Explorer
What the Head Said: Internet Explorer 9′s problematic console object
Working on a web application and find the Firefox error console to be indispensable.
However I recently upgraded to FF 4 and now when I click errors in the console, the source code doesn't come up like it used to. Not sure it's related to the upgrade but timing is about right.
I've looked over about:config options, made sure the console is enabled, etc. Spent a long time with google trying to find someone else with this problem... nothing.
I get the "hand" cursor when hovering over the URL as if clicking it will do what I expect. However, nothing at all happens. Nada.
I've looked around for hidden windows and even tiny ones but can't find anything...
Any ideas?
Well, I can't exactly figure out why this is happening, but I did find that it only happens when I have the Error Console window on a different display as the main window. I use 2 displays to make debugging easier and moving the error console window to the main display makes it work again.
On a Mac, FWIW.
Got this page which has some javascript on it (very heavy) and I am trying to see what happens when I click a certain element. However looking at the code there is no onclick function - the javascript is several JS files so take far to long to browse.
Is there a way with Firefox (firebug), Chrome or even IE to view whats / log what is happening when I click on an element in the browser?
In firefox (and this is also available in chrome and IE in another form) install addon firebug (if not installed). Go to Tools->Birebug->Open Firebug. Click on Left Icon and ask for tracing.
You can then trace your program.
Another way is to cause a breakpoint when you start, and you manually follow the execution of the script.
Chrome Developer Tools shows all attached event handlers for an element. See the section on Event Listeners towards the end.
#wizzard, try this: firebug - profiling button
ff only, but there is a lite version for chrome for example
I am logging using the jQuery.log plugin (which logs to console.log if available) and I am not seeing any of the logging messages appear in the Chrome JavaScript console.
Logging works on Firebug's console under Firefox, but I did have to explicitly enable the Firebug JavaScript console. Have a missed some option somewhere under Chrome?
Edit:
The only thing being logged to the console is
Uncaught Syntax error, unrecognized expression: |button
I assume that the Chrome console is suppose to log statements even after errors like the one above, but there may be some kind of issue with Chrome here, see http://code.google.com/p/chromium/issues/detail?id=29062. I am using Chrome 5.0.375 under Linux and that bug is listed as a Windows XP, Chrome 4.0 issue, it could still apply.
I've just had the same problem and found this question when trying to find an answer.
What fixed this for me was disabling firebug lite in chrome.
It was swallowing all console messages.
Make sure you have the console showing and that it is showing "All".
The cursor is on the button to hide/show the console.
Update: In newer versions of Chrome, you need to click the filter icon, then make sure "All" is selected.
When playing around with example Chrome Extensions, I was often unable to see the console.log messages when looking at console (ctrl+shift+j). But then I realized, that I was in the wrong place.
Wrench -> Tools -> Extensions and then click on the appropriate link under "Inspect active views". (in the Chrome examples it is often background.html) This should bring up the console that you are looking for.
On my computer I had accidently clicked the Debug filter. This made my log messages hidden. Here's how it was before (hidden messages):
Here's how it was after the change (working messages):
I am not sure if this is the case, but if you are using firebug with chrome, you have to turn firebug off in order for console.log() to work in Developer Tools.
I just found out logging was disabled from my filters.
For me, it was because the script was being cached and the browser was not loading my latest version.
Try Ctrl+F5 to reload your page.
Resetting default setting works for me.
While in the console tab, pressingF1 should open the setting page. There you will different settings that you can adjust including the button Restore defaults and reload.
I have this error by have obfuscated javascript code, deobfuscate and console.log work again)