google-chrome-devtools

Something is wrong with my Chrome inspector, I would like to reset the Chrome inspector to out of the box settings. How could I do ? (wihout removing my whole Chrome) Find the following two files and delete them. These files contain the settings for the inspector. chrome-devtools_devtools_0.localstorage chrome-devtools_devtools_0.localstorage-journal Please make sure to restart the Chrome again. Hope this helps. Aamer Shahzad Open DevTools by pressing F12 or ctrl + shift + i press F1 or click on ... on the top right corner beside cross to open settings scroll at the bottom or to the right of

In Chrome's JavaScript console: > function create(proto) { function Created() {} Created.prototype = proto return new Created } undefined > cc = create() Created {} > cc Created {} Created is a function private to the create function; after create completes, there are no (known to me) references to Created . Yet Chrome can show the function's name at any time, starting from the object created by it. Chrome didn't achieve this by following the "naïve" approach: > cc.constructor function Object() { [native code] } > cc.toString() "object [Object]" and anyway, I didn't set constructor on the

I'm profiling javascript application using Chrome dev tools. I see that the only memory area that grows is System objects total. I wonder how could I understand what causes such behavior as there are no details in the tool showing which system objects got leaked. I've taken a look at app allocation, but it doesn't change much over time ... When I'm using timeline feature heap grows over 500mb According to the JSHeapSnapshot.js implementation in Chromium, as mentioned in a comment by wOxxOm, a comparison for the a given node distance to 100000000 is performed ( distances[ordinal] >=

The code is meant to output the current tab object for the page the user is viewing to the console but it just outputs undefined. It's run from within a browser action page. chrome.tabs.getCurrent( function(tab){ console.log(tab); } ); I've looked at the documentation and as far as I can tell the code seems to match what it says. Try: chrome.tabs.getSelected(null, function(tab){ console.log(tab); }); The method getSelected() has been deprecated since Google Chrome 16 (but many articles in the official documentation had not yet been updated). Official message is here . To get the tab that is

A bunch of code isn't working and I'm trying to identify where the problem lies but console.log() isn't logging any results in Chrome Dev tools, am I doing it correctly? $(window).scroll(function() { $('section').each(function(){ var id='#'+$(this).attr('id'), off=$(id).offset().top, hei=$(id).height(), winscroll=$(window).scrollTop(), dif=hei+off-($(window).height()); if (winscroll >= off && winscroll<=dif) { console.log('first broken'); $(id+' .sticky').removeClass('abs').addClass('fix'); } else if (winscroll > dif){ console.log('second broken'); $(id+' .sticky').removeClass('fix').addClass(

How to find out which file and line a variable was defined in using google chrome console? For example, the variable Native (from MooTools) has been defined in global scope. I want to know in which file that defined this variable using google chrome console. zessx Using chrome : Open the Web Inspector Show the console and check if the var you're searching for exists (ex : Native Enter ) Click on the Resources panel Enter Native= , var Native or Native = in the top right search field You've got your result ! Here, there's only one result for the Native= search. The result is automatically

A Chrome Kiosk application that I wrote has a problem only when running in Kiosk mode on a Chromebox. When staring the application manually after I log into the Chromebox it runs well. Also when testing the application on my development machine everything works well. How can I attach a remote debug session, write remote logging information or in any other way get debugging information from the Kiosk application on the Chromebox to my development machine? If you run Chrome with the --remote-debugging-port=9222 option it will provide access to DevTools at http://localhost:9222/ . Now, on a