locked
Attempted to read or write protected memory in Server RRS feed

  • Question

  • User1979460985 posted


    Server Error in '/' Application.

    Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:


    [AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.]
    Telerik.WebControls.xf6f69499b80603a9.x50dd21ac842a034e(Object x7b4605021f5c01b7) +0
    Telerik.WebControls.RadGrid.RenderContents(HtmlTextWriter writer) +65
    Telerik.WebControls.RadGrid.Render(HtmlTextWriter writer) +248
    System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
    System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +253
    System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output) +87
    System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +53
    System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
    System.Web.UI.Page.Render(HtmlTextWriter writer) +38
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4240

    Version Information: Microsoft .NET Framework Version:2.0.50727.5456; ASP.NET Version:2.0.50727.5456

    Wednesday, August 22, 2012 2:03 AM

All replies

  • User-902516579 posted

    Hi,

    My understanding of this kind of error is that it happens in native code when the size of the variables content exceeds the allocated memroy for that variable.  So when the OS writes the value to memory the addresses get messed up and where the operation needs to go to next is corrupted, this is similiar to a buffer overflow error.

    The solution is to attempt to reproduce this issue, once you have a case where you can reproduce it, contact the company who created the code and request fix for it.

    HTH, Ben

    Wednesday, August 22, 2012 9:44 AM