Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 11, 2013 04:06 PM by davidfowl
Feb 21, 2013 07:16 PM|LINK
The issue seems well expressed in their GitHub project, haven't seen any action on it though. The cause still seems to be the PerformanceCounterManager class.
The only workaround I've been able to come up with is to pause the execution before and after the maphubs call. I simply add 3 breakpoints, one before the maphubs call, one on the maphubs call and one afterwards. Let it sit at each breakpoint for a few
seconds before continuing. I can get my iis express to spin up properly by doing this.
It seems to work fine once its published to our server running full iis.
Feb 22, 2013 04:48 AM|LINK
hmm havent got this problem yet , have dlls from rc1 in my solution.
did you guy update signalR dlls before you started getting this issue ? you can try going back to the prev versions.
also if this breakpoint thing works for you and issue is with PerformanceCounterManager
class then we can put Thread.sleep stmt as well for developement scenario.
Feb 22, 2013 10:59 AM|LINK
For us, the ability to have performance counters is not really of any great utility.
I mean, sure, eventually in production it would be great to be able to provide usage metrics, etc, etc.
But as long as everything just works, thats whats important, right?
Wouldnt it be better to have a switch to just turn them off/on right at the start?
That way we wouldnt encounter situations like previously, where several seconds passed while each error was thrown?
(And potentially it might even save a few cycles in production if they were disabled?)
Feb 22, 2013 11:08 AM|LINK
The last resort if we can't find any possible fix is to add a switch. As for your comment about "saving a few cycles" in production, that point is completely moot as the overhead performance counters adds is minimal. I'm not a fan of adding configuration
options to work around a bug somewhere.
Once we figure out why it happens we'll evaluate the options and pick what we think is best. I understand it's blocking people today so hopefully this doesn't drag on for several releases.
Feb 22, 2013 12:12 PM|LINK
We have another potential fix for this issue for anyone willing to try it out in the
perf-counter-fix branch. If you don't know how to git, you can download the source
here, build a copy and let me know if it solves the issue.
Feb 25, 2013 03:05 AM|LINK
I'm new to SignalR, just starting to experiment with it. I'm running Windows 8 Pro with VS2012 update 1. I created an ASP.NET Empty Web Application, added "RouteTable.Routes.MapHubs();" to my global.asax.cs file at the beginning of my Application_Start
function (this is the only line in the function), and added a default.aspx file with simply the word "hello" in the body. IIS Express hangs, but if I switch to "Use Visual Studio Development Server" instead of "Use Local IIS Web Server" in the "Web" section
of the web site properties, then I get a browser window with "Hello". If I switch back to Use Local IIS Web Server, it just hangs. If I comment out the line "RouteTable.Routs.MapHubs();" then it works in both. I'm about to try to learn to use this SignalR
thing but if I can't get it to just say Hello then it probably won't turn out too good.
Feb 25, 2013 03:09 AM|LINK
I'm guessing you read the thread right? Details are in this post about what is happening and that there's an active investigation to find out why it happens.
Feb 27, 2013 01:16 PM|LINK
I remember from an early release that I had the same problem. It has been a while ago but isn't here an executable that adds the performance counters to Windows? This was the problem for me because it coulnd't find the PC's.
Mar 11, 2013 01:04 PM|LINK
Any chance this could get merged into master and a new NuGet be pushed out? We use NuGet for our dependencies so currently our team needs to manually replace the DLL after each build, and our build server isn't happy.
This solution does fix the problem for me still, so I'd like to see it actually released.
Mar 11, 2013 04:06 PM|LINK
It was fixed a while ago and a new version of SignalR was released to
NuGet with this fix. See the release notes https://github.com/SignalR/SignalR/blob/master/ReleaseNotes.md#bugs-fixed