Yeah I think that's more of an environment issue and I don't think we have enough info to come up with a reasonable theory around it
@K On 30 March 2012 08:48, harlam357 <[email protected]> wrote: > Hi Krzysztof, > > Thanks for the reply. :) > > This happened to a user in the wild and I cannot reproduce it myself > in any fashion. Either in my full code base or as you suggest, in an > empty 3.5 console project. > > In my dealings with mixed mode (managed/unmanaged) code, an exception > with a signature of, System.AccessViolationException: Attempted to > read or write protected memory, generally means a buffer was overrun, > an array was walked off of, or some other unsightly deed was done to > unmanaged memory. However, I looked at the code for the > SubSystemConstants class and it's just string initialization. Nothing > that even remotely comes clone to saying, "memory corruption". > > If you have any idea that's fantastic. If not, please don't worry > about it. I don't want to take up your time. This happened to one > user of my application and if it was a widespread issue I'd be hearing > it from more than one person. I only posted it here because the stack > trace fell directly into the Windsor code base and thought you might > be able to give me a quick explanation. > > Thanks for all the work you do for the community! > > Kind Regards, > -H > > On Mar 27, 7:25 pm, Krzysztof Koźmic <[email protected]> > wrote: > > Does it happen if you just create a trivial empty .NET 3.5 solution with > > console project that just creates the container? > > > > @K > > > > On 28 March 2012 02:11, harlam357 <[email protected]> wrote: > > > > > > > > > > > > > > > > > One of my users has experienced the following exception. I am using > > > Windsor v2.5.3 .net v3.5 binaries. > > > > > My code simply instantiates a new container as such: IWindsorContainer > > > container = new WindsorContainer(); > > > > > System.TypeInitializationException: The type initializer for > > > 'Castle.MicroKernel.SubSystemConstants' threw an exception. ---> > > > System.AccessViolationException: Attempted to read or write protected > > > memory. This is often an indication that other memory is corrupt. > > > at Castle.MicroKernel.SubSystemConstants..cctor() > > > --- End of inner exception stack trace --- > > > at Castle.MicroKernel.DefaultKernel.RegisterSubSystems() > > > at Castle.MicroKernel.DefaultKernel..ctor(IDependencyResolver > > > resolver, IProxyFactory proxyFactory) > > > at Castle.Windsor.WindsorContainer..ctor() > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Castle Project Users" group. > > > To post to this group, send email to > [email protected] > > > . > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > >http://groups.google.com/group/castle-project-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
