I am on Windows 7, using IE8 and Visual Studio 2005. I have been enjoying the built in javascript debugger in IE8 for several months. About 2 weeks ago, I installed some security update for IE 8 (possibly KB978207) and all of a sudden the javascript debugger is now broken.
If I get a warning from IE 8 that an error occurred and asking if I want to debug using the built in debugger, if I hit yes, I get a grey popup in the top left corner (which I've never seen before) saying "JScript Debugger. Breaking on JScript runtime error - Object doesn't support this property or method". Then nothing happens. IE freezes up and then I get a Windows popup saying that IE 8 is no longer responding and asking if I want to end this process. If I try to end the process, nothing happens and I continue to get the grey popup. I usually have to kill debugging process from VS 2005, but the frozen IE8 still is present. It's not until later when the OS, finally cleans up the process that it will go away...
Edit (new info):
I tried removing the lastest security update and a silverlight update that came around the same time, but Windows automatically reinstalled them....
I then tried removing IE 8, and then adding it back to my system to reset anything related to IE8. This did not have any effect.
After reinstalling IE8, I did notice that, when I first tried to open the developer tools window by hitting F12 from a regular IE 8 window, I never saw anything, but I could see the developer tools title in the task manager list. I had to right click on the task and maximize the window, so I could actually see the developer tools window. Apparently this is a bug mentioned here: http://social.msdn.microsoft.com/Forums/en-US/iewebdevelopment/thread/79b8ee54-c5f6-4467-ba6d-27491c95cd13
I've realized that the window will maximize if the iexplorer.exe process is not the debugged process launched from VS2005.
The grey popup I mentioned in my original post is from the developer tools window iexplorer.exe process.
If I launch my app from VS2005 and then hit F12, I see that the developer tools window is opened (I can see that window is opened under the IE icon in my taskbar), but it is not shown. If I try to maximize it from the task manager, this has no effect.
So basically, the developer tools window is freezing up when it tries to open under my debugged iexplorer.exe process launched from VS2005. The OS then asks if I want to kill the process since it's not responding, but it is unable to kill it. At some later point, the zombie iexplorer.exe process is killed succesfully (by the OS I presume).
Had the same thing happening. You clued me in on the solution by pointing out F12 starts Developer Tools in the taskbar but doesn't show up on the screen. Apparently the window is off screen in nowhere land and causes major screwups if you attempt to debug in this state. So my solution was to:
Close all IE instances
Start up IE
Start up Developer Tools (F12)
Hover cursor over the the IE button on the taskbar until context menu shows
Right-click the Developer Tools item in the context menu (not the taskbar button)
Click "Move"
Start tapping arrows until you see the window come back in view. Mine was off stage left so I had to hold down the right arrow.
The window will have been sized down to just a window title bar, so resize by dragging the right corner down and out.
Once the window is moved back and resized, close it to "set" the position. You should be good to go now.
May be the security patch has disabled script debugging in IE. It was a common problem when using the debugger of VS 200X
Now on try to enjoy FireFox with the FireBug Addon. It's really great to debug Javascript. :)
Related
In a vue web application, I have the issue that I have some deep links (example.com/app/some/123) that are handled by the application (vue-router).
Sometimes (not always), for whatever reason when clicking such a link (in Outlook or from a desktop shortcut) when no browser window is opened, Chrome starts but immediately freezes (tab becomes unresponsive).
It feels like there is some redirect loop going on in my application code that causes this freeze. But my issue is that I have no clue on how to debug this to find the spot:
Opening the devtools is possible using the menu but JS files/code does not "load" - Scripts tab stays empty
Clicking the pause button does nothing, the same applies to pressing F8 (pause script execution)
The profiler cannot start (stays at "initializing").
I also have the feeling that this happens when a new version of the app (js bundle) is published but Chrome has some previous version cached. It feels this more often produces the issue. But this is just a guess.
Clicking the pause button/F8 is my regular procedure to tackle such things to find the spot where we are in the JS code at the moment. But unfortunately, here, this does not work as most of the browser is unresponsive.
The only way to close Chrome is to kill it via the task manager.
Is there any way to enable additional logging via Chrome settings or activate an "immediate debug session" right when the browser process starts to somehow get closer to the JS code that freezes the whole tab?
So ideally that somehow, right from the browser start, a profile of the "debug session" is saved even if the browser is process-killed that can later be inspected?
You could try webQsee (https://chrome.google.com/webstore/detail/webqsee-web-sniffer-recor/gamdpfnfkjknkimfbboonmgdfnondfme). The extension provides some usefull export features that might help you identifying the root cause.
Event Snapshot
Exports Screenshot, Cookies, Network and Console output. A lot of info but it is a proprietary format, in can only be analysed in the extension itself.
Excel Export
Like an HAR export, but also including Console output.
These two export options (and more) are available via the export menu located at the bottom of the extension window.
I'm just moved to windows 10.
And have latest version of Google Chrome on it.
But whenever I tried to access developer’s tool it shows nothing.
I have tried,
1) Right Click + Inspect element.
2) F12.
3) Right corner tab on Google chrome + more tools + developers tool.
But none of them working.
Please help.....
I don't know what is missing.
I had the same issue but in my scenario I was on a Virtual Machine with some complex display settings. The procedure here worked for me in other contexts:
You should see the process in the Windows bar on the bottom of your screen.
When you click on it, nothing is shown.
Bring back in the viewport
If the conditions above apply, then the window is simply displayed out of the display viewport. TO bring it back, do the following:
Make sure you have selected the window in the Windows bar.
Hit ALT + SPACE to show the menu
Select "Maximize".
The window should appear in one of your monitors.
Drag it around and resize it.
You should try also Ctrl+Shift+I for windows as written on the following doc
https://developers.google.com/web/tools/chrome-devtools/
I fixed this of this way
Open chrome dev tools
using the chrome page that you need debug press Win + "<" (left arrow)
windows ask you which window you want to the right and select chrome dev tool icon, but click should be in the icon instead of the rectangle of the windows
Just had the same problem. The window is apparently minimized.
On windows, hold the mouse on the chrome icon in the taskbar, when the thumb shows up, right click on it and select maximize window.
First thing i would try is closing all processes and restarting Chrome and if that doesn't work i would uninstall and reinstall chrome
I know this isn't really an answer but hope it might help
Goodluck!
Chrome -> Setting -> Extensions (Side Menu) -> Turn on Developer Mode
Had the same issue, The thing is just minimized. Hover over the side of the options at the bottom and drag to top and you will see the options.
see following image and hover over ht area highlighted in yellow
Your dev-tool might be on your second monitor, which you are not looking at but connect with your PC.
Disclaimer: Please try this at your own risk, I'm not fully aware of its consequences. It apparently clears chrome's local storage for all websites
All the solutions I saw didn't work for me, but this one did:
I deleted this folder:
// AppData\Local\Google\Chrome\User Data\Default\Local Storage\leveldb
Trying to debug a problem that's IE-11 specific, I would like to see the console messages logged when a certain control is clicked. But the control refreshes the page, which makes F12 tools automatically clear the console, so whatever is logged just before that, I don't get to see!
Past versions of IE had an option to keep the console contents on navigation. Is this option available in IE11? If so, where is it? If not, is there some other way to view the console that doesn't immediately discard the message I want to see?
In with the latest F12 update to IE11 (that came as part of the Win8.1 Update) there is now a button to disable "Clear on Navigate"
Additionally, you can enable IE to record messages in the Console at all times instead of only when the Console is open.
For all the changes to the IE11 F12 dev tools see: http://support.microsoft.com/kb/2929437
Ran into this and I didn't find a good solution, but I found a hacked one that worked well enough for me to debug.
Use window.onbeforeunload to pop up a window so you can at least see the values before they are purged.
See: Prompting and preventing user from navigating away/closing a page
I am using Internet Explorer 8, by choice. I need to debug a script in it. However, no matter how many times I click the Developer Tools Icon, under Tools or when I click F12 it will not show up. Sometimes, I can see that it is minimized in the taskbar but when I actually go to click it. It will not show up...
You may do Alt+Spacebar, then hit ‘m’ and start using your arrow keys to move the window around. And also check that link
When I step through code in Chrome's JavaScript debugger, I regularly run into a situation where a variable tooltip gets stuck and stays on screen, obscuring code that's behind it. Clicking off the tooltip or on other scope variables doesn't help, and the only way to fix this is usually to close and reopen the Inspector pane, which ends the debugging session.
Is there any better way to hide the tooltip when it decides to stick around?
I am getting this same problem in safari 5.1.1 on mac OS 10.6, very annoying, I have to close the web inspector - not just minimize - and reopen to get rid of it and it happens often.