Does anybody here experience the error shown below that starts at Go.... Our site just got a ton of this error. The "Go..." method has some random number after it (i.e. Go564378, Go564478, etc.), that leads me to thinking if our site is being attacked or was hacked. The rest of the stack trace remains exactly the same except for the first line at the "Go..." method. Thoughts?
System.OutOfMemoryException:
at Go564378 (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Text.RegularExpressions.CompiledRegexRunner.Go (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Text.RegularExpressions.RegexRunner.Scan (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Text.RegularExpressions.Regex.Run (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Text.RegularExpressions.Regex.IsMatch (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Text.RegularExpressions.Regex.IsMatch (System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at Umbraco.Core.Persistence.Database.AddSelectClause (Umbraco.Core, Version=1.0.6634.25789, Culture=neutral, PublicKeyToken=null)
at Umbraco.Core.Persistence.Database+<Query>d__74`1.MoveNext (Umbraco.Core, Version=1.0.6634.25789, Culture=neutral, PublicKeyToken=null)
at System.Collections.Generic.List`1..ctor (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Linq.Enumerable.ToList (System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at SEOChecker.Core.Repository.Umbraco.UmbracoDomainRepository.GetRootNodes (SEOChecker.Core, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at SEOChecker.Core.Repository.Umbraco.UmbracoDomainRepository.GetDomainNodes (SEOChecker.Core, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at SEOChecker.Core.Repository.Umbraco.UmbracoDomainRepository.GetRootNodesForDomain (SEOChecker.Core, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at SEOChecker.Core.Repository.Umbraco.UmbracoDomainRepository.GetRootNodeForDomain (SEOChecker.Core, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at SEOChecker.Core.Extensions.HttpContextExtensions.GetNotfoundPageConfig (SEOChecker.Core, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at SEOChecker.Handlers.NotFoundHandlers.Inbound404Handler.Execute (SEOChecker, Version=1.10.1.0, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.Routing.ContentLastChanceFinderByNotFoundHandlers.HandlePageNotFound (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.Routing.ContentLastChanceFinderByNotFoundHandlers.TryFindContent (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.Routing.PublishedContentRequestEngine.HandlePublishedContent (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.Routing.PublishedContentRequestEngine.FindPublishedContentAndTemplate (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.Routing.PublishedContentRequestEngine.PrepareRequest (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.UmbracoModule.ProcessRequest (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at Umbraco.Web.UmbracoModule.<Init>b__12_2 (umbraco, Version=1.0.6634.25796, Culture=neutral, PublicKeyToken=null)
at System.Web.HttpApplication+SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute (System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Web.HttpApplication.ExecuteStepImpl (System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Web.HttpApplication.ExecuteStep (System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
Seems like to occur during SeoChecker trying to resolve the 404 page.
Regex could cause memory leak.
Perhaps check with Soeteman if this is known to them?
OutOfMemoryException
Does anybody here experience the error shown below that starts at Go.... Our site just got a ton of this error. The "Go..." method has some random number after it (i.e. Go564378, Go564478, etc.), that leads me to thinking if our site is being attacked or was hacked. The rest of the stack trace remains exactly the same except for the first line at the "Go..." method. Thoughts?
Seems like to occur during SeoChecker trying to resolve the 404 page. Regex could cause memory leak. Perhaps check with Soeteman if this is known to them?
is working on a reply...