Visual Studio + Chrome = 100% CPU - performance

I'm developing an application - something I've done on the same machine for the last x years.
I'm still using XP on this machine - VS 2010. I've also recently changed from the default dev host to IIS 7.5.
At them moment, I'm checking out Google Polymer - this is where the root of my problem lies. When I click on a trivial link to open a dropdown menu, the CPU goes into overdrive and stays there. This only happens on Chrome, not Firefox.
I eliminated a rogue polymer installation by linking direct to the polymer site url's.
I paired the page down so its just html - no aspx.
I put the page up on codepen and I do not get the same issue.
I removed all extensions from Chrome and reset my settings.
I switched betwen IIS and the default dev host.
After these tests, the only variant is that copepen runs the page and I run the page. Therefore my conclusion is that it must be something to do with VS or IIS/dev host.
I'm scratching my head as to where to go next with this. Has anyone else had similar experiences when testing on Chrome?
Help!

Confirmed here : VS 2013 (32bit) + Google Chrome = 100% CPU Windows 8 & 10
You need to diable BrowserLink option in the VS 2013
here is how you can disable it
http://www.asp.net/visual-studio/overview/2013/using-browser-link#disabling

After liasing with the guys from polymer project for sometime, I decided that polymer wasn't ready for production just yet.

Related

Why did my Microsoft Add-in suddenly stop showing as an option in F12 devtools?

At one point I was able to see our Outlook add-in app in the target options in f12 devtools for troubleshooting, but sometime last month it stopped showing up there. My colleagues are stumped, and I can't find much online in the way of troubleshooting.
I tried checking my Windows version and Outlook version against others who can see it in their devtools, but we're all on Windows 10 enterprise v1803, Outlook v1910, and IE 11. I've tried many things over the month since this happened like rebooting my PC, making sure I have the latest updates from IT, refreshing the options, running some commands I found online for targeting the right browser for devtools, etc. No change.
Another peculiar thing is that I'm seeing some completely different things in the Add-in than they are, like button alignments and div widths and such. I had our dev environment looking perfect on my end, but when a few people on the team screenshared with me there were a number of styling issues I can't reproduce. Even weirder, nobody experiences these issues in O365, it's just the desktop Outlook app on our Windows machines.
Any ideas on how to troubleshoot this would be very greatly appreciated.
Steps I take to produce the issue:
Click on manifest icon for our app in Outlook ribbon. App loads in the sidebar.
Open F12 devtools (both 32 and 64 bit for good measure from the System32 and SysWOW64 directories).
App is not in the target list. Click refresh, still not in the list.
FYI, any IE 11 windows I have open show up there, just not my app.
Starting in Windows 10 version 1903, the latest version of Office will use Edge WebView instead of IE to render add-ins. Edge WebView requires a different debugger (not the F12 debugger) called Microsoft Edge DevTools. You can find out more about it here.

Cannot see default web site in iis in windows 10

I got new pc in office and I had installed IIS from windows feature (on/off) and everything appears good.
When I started iis manager I can just see my pc name i.e.
MyPCName (MyDomainName\MyUserName)
thats it. I can't see anything else. Expanding server doesn't show anything. Right clicking on it just giving three options -
Refresh
Rename
Switch to Content View
I can't see any other option. So far I had re-installed it multiple times. and restarted my pc multiple times, but nothing changed.
Can anyone help?

Visual Studio with Web Essentials, unused CSS is not working

I am working on a .NET 4.5.1 project in Visual Studio and have Web Essentials installed and functioning in all other ways except finding unused CSS. When I test with a new project, it works as expected.
Is there a known situation in which Unused CSS will not work?
Environment:
VS2013 Pro
Win7 Pro
Steps to reproduce:
Start debugging the app in Chrome
Once the site opens in a new tab, select Start Recording in the Browser Link Dashboard
Change content by clicking through the site
Results:
Recording has started and Stop Recording is now available
There are no messages sent to the output window
Clear CSS Usage Data option in the Browser Link toolbar (in the top menu) is disabled. It never is enabled whether recording or not.
Expected:
Messages in the output view
Ability to clear CSS usage data
Attempts to troubleshoot:
Installed prior version of extension - same result
Verified the issue exists on Chrome, Firefox and IE
Other features of Browser Link work as expected
Creating a new project works as expected and "Clear CSS usage data" is not greyed out
Browser Link drop down menu
I know it's a long time since you asked this, but this solution might actually help someone else...You can identify unused CSS using Chrome Dev tools
Open your chrome Dev tools
Click on the Audits tab
Click on Run at the bottom, wait for the audit to finish
You will get unused CSS under Remove unused CSS rules in the Web Page Performance section

Silverlight not working in Firefox 3.6.12

We are having some wierd behavior in firefox with silverlight. We have tried everything and I am hoping for some more ideas. Below is the behavior
Install firefox (3.6.12) and silverlight (4.0.50917.0). The versions there are locked and not controlled by us and on all our users machines.
Visit our silverlight application (also tried simple application with just a background)
Instead of seeing our application, you see "Get Microsoft Silverlight"
-- (about:plugins reports silverlight 4.0.50917.0 installed and enabled)
Visit site in IE, app works
Install or uninstall any plug-in (tried Firebug and IETab2)
After install, click "Restart" when prompted
After FF restarts, silverlight works as expected
Close firefox and reopen.
Once again, silverlight is broken
Any ideas? We tried the CWDIllegalInDllSearch entry in the registry to no avail. Please help!
I think it is a problem with Firefox that has been fixed with Version 3.6.14. See this BugReport on Bugzilla. A memory leak in prior versions, cause some problems in the Silverlight detection script of Firefox.
I can only suggest to update Firefox to version 3.6.14. But before i would try it in a local test environment to check if its really a bug in Firefox.
Update:
It seems to be a general problem with Firefox 3.6.x, cause some users report the same error as your with higher versions than 3.6.14. See here and here.
The only thing that springs to mind is disabling the plugin-container
In Firefox address bar type about:config
Read the warning, choose your preference to always remind you or not and accept
In the search bar of the config options now type: npctrl
You should then see the entry: dom.ipc.plugins.enabled.npctrl.dll
Change the value from true to false (simply double-clicking will change this for you)
Restart Firefox
EDIT
There is another workaround which is to disable then re-enable silverlight plugin. Rather than re-isntalling.

Entity.Include() + local IIS development setup + Chrome = long browser requests

I have an ASP.NET MVC3 web application with EF Code First. It's set up to debug using my local IIS (as opposed to the Visual Studio 2010 Developer Server). I also have Google Chrome set as my default browser.
If my repository layer uses the .Include() method, Chrome takes at least 10 seconds to return the page, usually more than 30 seconds. I can step through the debugger all the way to the View very quickly, and yet Chrome still takes that long to finish serving the page.
This problem goes away if I do any of the following
Take out the .Include()
Use IE or Firefox
Use VS Development Server instead of local IIS
I have no idea why this would happen, or how to further troubleshoot it.
Turns out it was the Glimpse NuGet package. I disabled it in my web.config and it works fine now.

Resources