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

2 posts, 0 answers
  1. Scott Davis
    Scott Davis avatar
    5 posts
    Member since:
    Apr 2010

    Posted 17 Apr 2010 Link to this post


    Hi,

    I'm getting this exception pretty regularly running my test :(

    It doesn't happen every time, but enough to make the tests unreliable and, well, kinda counterproductive really.

    Here is the callstack:

    ArtOfTest.WebAii.dll!ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(ArtOfTest.WebAii.Messaging.Process.BrowserCommand request = {BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_0678d0ed-37cb-4923-a273-7529c9ca8061',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')}) + 0xe3 bytes
      ArtOfTest.WebAii.dll!ArtOfTest.WebAii.Core.Browser.ExecuteCommand(ArtOfTest.WebAii.Messaging.Process.BrowserCommand request = {BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_0678d0ed-37cb-4923-a273-7529c9ca8061',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')}, bool performDomRefresh = false, bool waitUntilReady = false) + 0x42 bytes
      ArtOfTest.WebAii.dll!ArtOfTest.WebAii.Core.Browser.RefreshDomTree() + 0x113 bytes
      ArtOfTest.WebAii.dll!ArtOfTest.WebAii.ObjectModel.Element.Refresh(bool forceDomTreeRefresh = true) + 0x33 bytes
      [Native to Managed Transition]
      [Managed to Native Transition]
      ArtOfTest.Common.dll!ArtOfTest.Common.WaitAsync.CallRefreshIfNeeded<ArtOfTest.WebAii.ObjectModel.Element>(ArtOfTest.WebAii.ObjectModel.Element target = {[Element: 'div:213' (id=ctl00_ctl00_Fcph_Mcph_portalBody_portalTabStrip)]}) + 0x261 bytes
      ArtOfTest.Common.dll!ArtOfTest.Common.WaitAsync._worker_DoWork<ArtOfTest.WebAii.ObjectModel.Element,object>(object waitParam = {ArtOfTest.Common.WaitAsync.WaitParams<ArtOfTest.WebAii.ObjectModel.Element,object>}) + 0x228 bytes
      mscorlib.dll!System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(object state) + 0x2f bytes
      mscorlib.dll!System.Threading.ExecutionContext.runTryCode(object userData) + 0x51 bytes
      [Native to Managed Transition]
      [Managed to Native Transition]
      mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x67 bytes
      mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x45 bytes
    mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(System.Threading._ThreadPoolWaitCallback tpWaitCallBack) + 0x53 bytes
      mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(object state) + 0x59 bytes
      [Appdomain Transition]

    You can see that it is transitioning into native code a couple of times, most likely where the memory corruption is coming from... 

    Has anyone else seen this also? I am using the BETA so maybe I should upgrade. I hope it goes away, could be very nasty to track down...

    Thanks!
    Scott

  2. Cody
    Admin
    Cody avatar
    3354 posts

    Posted 20 Apr 2010 Link to this post

    Hi Scott Davis,

    Thank you for the stack trace. Unfortunately it only tells us a part of the story. What exception was thrown that generated the stack trace? Which step in your test failed (is it the same step that always fails?)? Am I correct in assuming that your test normally passes but only occasionally fails at unexpected times? How frequently?

    At the end of your message you mention you're using Beta. Which Beta version are you using? We did just release WebAii testing framework 2010.1.4.12 last week. You may want to give that version a try.

    Can you send us your test to study?

    All the best,
    Cody
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top