What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 128 Stack Exchange communities.

Cannot click on any proposal, no matter whether it is in newest, beta, hottest... well, actually, for a moment I could click on a couple, which pressed back and another, back and another, to see if they were up, but soon after it was down again, including ones I had previously clicked on. This is the first time I have visited this site. Looks Very interesting.

Is it down for everyone? Any idea when will it be back up?

share|improve this question
1  
Repro'd and passed along to developers. –  Dori Jun 19 '11 at 4:46
1  
Confirmed - Chrome 12 on Mac OSX 10.6.7. –  Neil Fein Jun 19 '11 at 5:05
1  
Confirmed - I get the Oops! Something Bad Happened! error on nearly every page, Chrome 13.0.782.24 beta-m on Windows 7 64-bit –  user161944 Jun 19 '11 at 5:48
    
Well it isn't just me then :) I'll check again later. –  Zahara Andrews Jun 19 '11 at 6:35
    
Working for me now. I could visit the Area 51 Japanese, German, and Skeptics proposals (and no they weren't cached) on OS X Safari 5, along with some other pages I randomly clicked on. Maybe it was fixed? –  Troyen Jun 19 '11 at 8:29
    
@Troyen - It's still crashing for me on OS X Safari 5. Last I heard, the theory was it might be related to which server you happen to hit. –  Dori Jun 19 '11 at 10:43

1 Answer 1

This should be fixed now, it was indeed related to which server you hit, one of the three web servers that Area 51 is load balanced to was eating it here, so you had a 1/3 chance of being jerked around.


Further reading:
I restarted the application pool and all is well now, for those curious it's this nasty little bug that pops up occasionally:

System.InvalidOperationException: Hashtable insert failed. Load factor too high. The most common cause is multiple threads writing to the Hashtable simultaneously.
   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   at System.ComponentModel.TypeDescriptor.NodeFor(Type type, Boolean createDelegator)
   at System.ComponentModel.TypeDescriptor.GetProvider(Type type)
   at System.ComponentModel.DataAnnotations.AssociatedMetadataTypeTypeDescriptionProvider..ctor(Type type)
   at System.Web.Mvc.ModelBinderDictionary.GetBinder(Type modelType, IModelBinder fallbackBinder)
   at System.Web.Mvc.ControllerActionInvoker.GetParameterValue(ControllerContext controllerContext, ParameterDescriptor parameterDescriptor)
   at System.Web.Mvc.ControllerActionInvoker.GetParameterValues(ControllerContext controllerContext, ActionDescriptor actionDescriptor)
   at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)
   at System.Web.Mvc.Controller.ExecuteCore()
   at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext)
   at System.Web.Mvc.MvcHandler.<>c__DisplayClass6.<>c__DisplayClassb.<BeginProcessRequest>b__5()
   at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass1.<MakeVoidDelegate>b__0()
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

We've been told it's being worked on by the guys at Microsoft, and it'll be in the next service pack - if it continues to be an issue we'll go the hotfix route.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .