![]() The text you eval can reference local variables of the function, and in the non-strict mode, you can even create new local variables by using eval('var foo = …'). Whenever you use eval() inside a function, a closure is used.Returning a function from inside another function is the classic example of closure, because the state inside the outer function is implicitly available to the returned inner function, even after the outer function has completed execution.Whenever a function is declared in JavaScript closure is created.The following will print `3`, three times. At some later point, the zombie iexplorer.exe process is killed succesfully (by the OS I presume).Ĭonst secret = unc(Math.random()*100)Ĭonsole.log(`The secret number is $ ) The OS then asks if I want to kill the process since it's not responding, but it is unable to kill it. So basically, the developer tools window is freezing up when it tries to open under my debugged iexplorer.exe process launched from VS2005. If I try to maximize it from the task manager, this has no effect. 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. The grey popup I mentioned in my original post is from the developer tools window iexplorer.exe process. I've realized that the window will maximize if the iexplorer.exe process is not the debugged process launched from VS2005. Apparently this is a bug mentioned here: I had to right click on the task and maximize the window, so I could actually see the developer tools window. This did not have any effect.Īfter 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 then tried removing IE 8, and then adding it back to my system to reset anything related to IE8. I tried removing the lastest security update and a silverlight update that came around the same time, but Windows automatically reinstalled them…. It's not until later when the OS, finally cleans up the process that it will go away… I usually have to kill debugging process from VS 2005, but the frozen IE8 still is present. If I try to end the process, nothing happens and I continue to get the grey popup. 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. Breaking on JScript runtime error – Object doesn't support this property or method". 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. 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. I have been enjoying the built in javascript debugger in IE8 for several months. Undocking did not help this time.I am on Windows 7, using IE8 and Visual Studio 2005. Update March 18, 2011: Same issue with trying to access SBS 2008 Remote Web Workplace. I’m glad it’s working for now, but I sure wish I knew what the problem was and what fixed it! What? What happened? What fixed it? Did I need to reboot after one of those regsvr32 calls? Is the problem permanently fixed? Just for grins, I tried booting docked again, with all drivers enabled. THAT worked! Okay so it’s something that only happens when docked–video? ![]() This is on a docked Lenovo ThinkPad T60p. I tried rebooting to Safe Mode with Networking (had to type in my Bitlocker key–that’s new). I tried re-registering C:\Program Files\Internet Explorer\ieproxy.dll, as suggested in a partner forum. I tried re-registering all the DLLs listed in MSKB 281679, even though about half of them fail to register in Win7. I tried MSCONFIG, disabling all non-Microsoft startup items, also suggested here. I tried resetting IE 8 to its default, suggested here. Sure enough, even when I right-click on a link and select Open in New Window, nothing happens. Unfortunately, no similar article exists for IE 8. That led to the modified article 281679 for IE 5 and 6. This stackoverflow article led me to the MSKB 180176 about the problem under IE4 (!). Make sure that ‘shdocvw.dll’ is a valid DLL or OCX file and then try again."). Google has many suggestions, mostly about using regsvr32 to re-register actxprxy.dll (which works) and shdocvw.dll (which fails with a message like "The module ‘shdocvw.dll’ was loaded but the entry-point DllRegisterServer was not found. Under Windows 7, Internet Explorer 8 was giving consistent messages when JavaScript tried to open a new window: "No such interface supported."ĭebugging mode shows that this is happening when trying to open a window:
0 Comments
Leave a Reply. |